CVE-2024-40984: Linux kernel · ACPICA: Revert "ACPICA: avoid Info: mapping multiple BARs.
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 7.8 High · fixed in 5.4.0-1132.142~18.04.1 : patch Linux kernel soon.
Data as of 26 Oct 2026, 23:28 UTC
- Patch
- Available – fixed in 5.4.0-1132.142~18.04.1, 5.4.0-1137.144~18.04.1, 5.4.0-1136.145~18.04.1 +71
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6999-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7003-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7003-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7004-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7005-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7006-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7003-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7007-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7008-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7005-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7009-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7019-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-ibmpkg:deb/ubuntu/linux-ibm?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: ACPICA: Revert "ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine." Undo the modifications made in commit d410ee5109a1 ("ACPICA: avoid "Info: mapping multiple BARs. Your kernel is fine.""). The initial purpose of this commit was to stop memory mappings for operation regions from overlapping page boundaries, as it can trigger warnings if different page attributes are present. However, it was found that when this situation arises, mapping continues until the boundary's end, but there is still an attempt to read/write the entire length of the map, leading to a NULL pointer deference. For example, if a four-byte mapping request is made but only one byte is mapped because it hits the current page boundary's end, a four-byte read/write attempt is still made, resulting in a NULL pointer deference. Instead, map the entire length, as the ACPI specification does not mandate that it must be within the same page boundary. It is permissible for it to be mapped across different regions.
References
- ubuntu.com/security/CVE-2024-40984 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-40984 (opens in a new tab)
- git.kernel.org/linus/a83e1385b780d41307433ddbc86e3c528db031f0 (opens in a new tab)
- git.kernel.org/stable/c/435ecc978c3d5d0c4e172ec5b956dc1904061d98 (opens in a new tab)
- git.kernel.org/stable/c/ae465109d82f4fb03c5adbe85f2d6a6a3d59124c (opens in a new tab)
- git.kernel.org/stable/c/6eca23100e9030725f69c1babacd58803f29ec8d (opens in a new tab)
- git.kernel.org/stable/c/dc5017c57f5eee80020c73ff8b67ba7f9fd08b1f (opens in a new tab)
- git.kernel.org/stable/c/ddc1f5f124479360a1fd43f73be950781d172239 (opens in a new tab)
- git.kernel.org/stable/c/434c6b924e1f4c219aab2d9e05fe79c5364e37d3 (opens in a new tab)
- git.kernel.org/stable/c/e21a4c9129c72fa54dd00f5ebf71219b41d43c04 (opens in a new tab)
- git.kernel.org/stable/c/a83e1385b780d41307433ddbc86e3c528db031f0 (opens in a new tab)
- ubuntu.com/security/notices/USN-6999-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7003-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7003-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7004-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7005-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7006-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7003-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7007-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7008-1 (opens in a new tab)