CVE-2024-57929: dm array: fix releasing a faulty array block twice in dm_array_cursor_end
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 017c4470bff53585370028fec9341247bad358ff, 6002bec5354f86d1a2df21468f68e3ec03ede9da, 738994872d77e189b2d13c501a1d145e95d98f46.
Low priority for now. Upgrade to Linux Linux 017c4470bff53585370028fec9341247bad358ff, 6002bec5354f86d1a2df21468f68e3ec03ede9da, 738994872d77e189b2d13c501a1d145e95d98f46 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: dm array: fix releasing a faulty array block twice in dm_array_cursor_end When dm_bm_read_lock() fails due to locking or checksum errors, it releases the faulty block implicitly while leaving an invalid output pointer behind. The caller of dm_bm_read_lock() should not operate on this invalid dm_block pointer, or it will lead to undefined result. For example, the dm_array_cursor incorrectly caches the invalid pointer on reading a faulty array block, causing a double release in dm_array_cursor_end(), then hitting the BUG_ON in dm-bufio cache_put(). Reproduce steps: 1. initialize a cache device dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --table "0 65536 linear /dev/sdc 8192" dmsetup create corig --table "0 524288 linear /dev/sdc $262144" dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 dmsetup create cache --table "0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0" 2. wipe the second array block offline dmsteup remove cache cmeta cdata corig mapping_root=$(dd if=/dev/sdc bs=1c count=8 skip=192 \ 2>/dev/null | hexdump -e '1/8 "%u\n"') ablock=$(dd if=/dev/sdc bs=1c count=8 skip=$((4096*mapping_root+2056)) \ 2>/dev/null | hexdump -e '1/8 "%u\n"') dd if=/dev/zero of=/dev/sdc bs=4k count=1 seek=$ablock 3. try reopen the cache device dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --table "0 65536 linear /dev/sdc 8192" dmsetup create corig --table "0 524288 linear /dev/sdc $262144" dmsetup create cache --table "0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0" Kernel logs: (snip) device-mapper: array: array_block_check failed: blocknr 0 != wanted 10 device-mapper: block manager: array validator check failed for block 10 device-mapper: array: get_ablock failed device-mapper: cache metadata: dm_array_cursor_next for mapping failed ------------[ cut here ]------------ kernel BUG at drivers/md/dm-bufio.c:638! Fix by setting the cached block pointer to NULL on errors. In addition to the reproducer described above, this fix can be verified using the "array_cursor/damaged" test in dm-unit: dm-unit run /pdata/array_cursor/damaged --kernel-dir <KERNEL_DIR>
- Published
- Jan 19, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-672
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 7.1
- CNA · Linux
- 7.8
- 0.7 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.9 and later · before 5.4.290
- linux linux kernel5.5 and later · before 5.10.234
- linux linux kernel5.11 and later · before 5.15.177
- linux linux kernel5.16 and later · before 6.1.125
- linux linux kernel6.2 and later · before 6.6.72
- linux linux kernel6.7 and later · before 6.12.10
- linux linux kernel6.13
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.9affected
- fdd1315aa5f022fe6574efdc2d9535f75a0ee255 and later · before 9c7c03d0e926762adf3a3a0ba86156fb5e19538baffected · git
- fdd1315aa5f022fe6574efdc2d9535f75a0ee255 and later · before fc1ef07c3522e257e32702954f265debbcb096a7affected · git
- fdd1315aa5f022fe6574efdc2d9535f75a0ee255 and later · before 738994872d77e189b2d13c501a1d145e95d98f46affected · git
- fdd1315aa5f022fe6574efdc2d9535f75a0ee255 and later · before e477021d252c007f0c6d45b5d13d341efed03979affected · git
- fdd1315aa5f022fe6574efdc2d9535f75a0ee255 and later · before 6002bec5354f86d1a2df21468f68e3ec03ede9daaffected · git
- fdd1315aa5f022fe6574efdc2d9535f75a0ee255 and later · before 017c4470bff53585370028fec9341247bad358ffaffected · git
- fdd1315aa5f022fe6574efdc2d9535f75a0ee255 and later · before f2893c0804d86230ffb8f1c8703fdbb18648abc8affected · git
- before 4.9not affected · semver
- 5.4.290 and later · up to and including 5.4.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.128-1 | 6.1.128-1 |
| Debian:13 | linux | before 6.12.10-1 | 6.12.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-57917Jan 19, 2025 · topology: Keep the cpumask unchanged when printing cpumap31Monitor
- ← EarlierCVE-2024-57924Jan 19, 2025 · fs: relax assertions on failure to encode file handles22Monitor
- Later →CVE-2023-52923Jan 20, 2025 · netfilter: nf_tables: adapt set backend to use GC transaction API22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 017c4470bff53585370028fec9341247bad358ff | Vendor (CNA) |
| Linux Linux | 6002bec5354f86d1a2df21468f68e3ec03ede9da | Vendor (CNA) |
| Linux Linux | 738994872d77e189b2d13c501a1d145e95d98f46 | Vendor (CNA) |
| Linux Linux | 9c7c03d0e926762adf3a3a0ba86156fb5e19538b | Vendor (CNA) |
| Linux Linux | e477021d252c007f0c6d45b5d13d341efed03979 | Vendor (CNA) |
| Linux Linux | f2893c0804d86230ffb8f1c8703fdbb18648abc8 | Vendor (CNA) |
| Linux Linux | fc1ef07c3522e257e32702954f265debbcb096a7 | Vendor (CNA) |
| debian:linux | 6.1.128-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2021-47069324 days apartipc/mqueue, msg, sem: avoid relying on a stack reference past its expiry28Monitor
- CVE-2024-5667423 days apartvirtio_net: correct netdev_tx_reset_queue() invocation point22Monitor
- CVE-2024-4995390 days apartnet/mlx5e: Fix crash caused by calling __xfrm_state_delete() twice22Monitor
- CVE-2024-4995590 days apartACPI: battery: Fix possible crash when unregistering a battery hook22Monitor
- CVE-2021-47294243 days apartnetrom: Decrease sock refcount when sock timers expire22Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-672 · Operation on a Resource after Expiration or ReleaseCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/6002bec5354f86d1a2df21468f68e3ec03ede9da
- git.kernel.org/stable/c/738994872d77e189b2d13c501a1d145e95d98f46
- git.kernel.org/stable/c/9c7c03d0e926762adf3a3a0ba86156fb5e19538b
- git.kernel.org/stable/c/e477021d252c007f0c6d45b5d13d341efed03979
- git.kernel.org/stable/c/f2893c0804d86230ffb8f1c8703fdbb18648abc8
- git.kernel.org/stable/c/fc1ef07c3522e257e32702954f265debbcb096a7
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.