s390/ism: folio_put() after error
- 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 6.6.158, 6.9, 6.12.111, 6.18.53, 7.2.7
- 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
Summary
In the Linux kernel, the following vulnerability has been resolved: s390/ism: folio_put() after error dmb->cpu_addr was allocated via folio_alloc(). Use folio_put() instead of kfree() in the error exit of ism_alloc_dmb() to avoid slab allocator corruption. While at it, reset dmb->cpu_addr after folio_put to avoid unintentional UAF by future callers.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 121fb75414ab8debafd548bded9d888cd5a8f165 · fixed in 90f6f5cb331af52b14c0f309fb27dc243e8e2982; From 83781384a96b95e2b6403d3c8a002b2c89031770 · fixed in 890e2ef726904d1d8328e4b9f5090eeb8761b9d1; From 83781384a96b95e2b6403d3c8a002b2c89031770 · fixed in eebb6a9017b55ac05be770cf7b89f9da49505ae7; From 83781384a96b95e2b6403d3c8a002b2c89031770 · fixed in 60983356fab0c1171c5cb1b56a36349ebadc608e; From 83781384a96b95e2b6403d3c8a002b2c89031770 · fixed in 907a56ab3eb8a58500a58daa76087f17bb2b6826; From 6.6.29 · fixed in 6.6.158; From 6.8.8 · fixed in 6.9
- Linux Linux
6.9
- KernelLinux
fixed in 6.6.158; From 6.7.0 · fixed in 6.12.111; From 6.9.0 · fixed in 6.18.53; From 6.13.0 · fixed in 7.2.7