block: fix potential invalid pointer dereference in blk_add_partition
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.227, 5.15.168, 6.1.113, 6.6.54, 6.10.13, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: block: fix potential invalid pointer dereference in blk_add_partition The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer. This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From b72053072c0bbe9f1cdfe2ffa3c201c185da2201 · fixed in 4bc4272e2506941c3f3d4fb8b0c659ee814dcf6f; From b72053072c0bbe9f1cdfe2ffa3c201c185da2201 · fixed in cc4d21d9492db4e534d3e01253cf885c90dd2a8b; From b72053072c0bbe9f1cdfe2ffa3c201c185da2201 · fixed in 64cf2a39202ca2d9df5ee70eb310b6141ce2b8ed; From b72053072c0bbe9f1cdfe2ffa3c201c185da2201 · fixed in 80f5bfbb80ea1615290dbc24f49d3d8c86db58fe; From b72053072c0bbe9f1cdfe2ffa3c201c185da2201 · fixed in 652039ba477c9a4ab43740cf2cb0d068d53508c2; From b72053072c0bbe9f1cdfe2ffa3c201c185da2201 · fixed in afe53ea9b378c376101d99d216f13b6256f75189; From b72053072c0bbe9f1cdfe2ffa3c201c185da2201 · fixed in 26e197b7f9240a4ac301dd0ad520c0c697c2ea7d
- Linux Linux
5.5
- KernelLinux
From 5.5.0 · fixed in 5.10.227; From 5.11.0 · fixed in 5.15.168; From 5.16.0 · fixed in 6.1.113; From 6.2.0 · fixed in 6.6.54; From 6.7.0 · fixed in 6.10.13; From 6.11.0 · fixed in 6.11.2
References 7
git.kernel.org
- stable/c/4bc4272e2506941c3f3d4fb8b0c659ee814dcf6f
- stable/c/cc4d21d9492db4e534d3e01253cf885c90dd2a8b
- stable/c/64cf2a39202ca2d9df5ee70eb310b6141ce2b8ed
- stable/c/80f5bfbb80ea1615290dbc24f49d3d8c86db58fe
- stable/c/652039ba477c9a4ab43740cf2cb0d068d53508c2
- stable/c/afe53ea9b378c376101d99d216f13b6256f75189
- stable/c/26e197b7f9240a4ac301dd0ad520c0c697c2ea7d