CVE-2026-98024
Severity not reportedData quality: partial.
Some fields were not provided by the source.
In the Linux kernel, the following vulnerability has been resolved: s390/ism: folio_put() after error dmb->cpu_addr was allocated via folio_alloc().
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.
CVSS
—
Awaiting analysis by NVD
Timeline (UTC)
Published: 2026-09-25 11:17
Modified: 2026-10-19 10:17
NVD status: Received
Last synced 3 days ago
Verified against the source API 2026-10-27 06:55 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).
Affected products
Not reported by the source (unknown — not "none").
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://git.kernel.org/stable/c/60983356fab0c1171c5cb1b56a36349ebadc608e 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/890e2ef726904d1d8328e4b9f5090eeb8761b9d1 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/907a56ab3eb8a58500a58daa76087f17bb2b6826 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/90f6f5cb331af52b14c0f309fb27dc243e8e2982 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/eebb6a9017b55ac05be770cf7b89f9da49505ae7 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Data sources
NVD CVE API 2.0 — fetched 2026-10-27 06:55 UTC · record ↗