Quick answers
- Is CVE-2026-98024 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98024 being exploited in the wild.
- How severe is CVE-2026-98024?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- Unknown Linux kernel Multiple stable versions (fix applied across linux-5.x through linux-7.x).
- Is there a fix for CVE-2026-98024?
- A patch was published on 2026-09-21. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-98024 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-98024?
- Check whether you run Unknown Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the ism_alloc_dmb() function in drivers/s390/net/ism_drv.c, where folio_alloc() allocates memory but the error path incorrectly calls kfree() instead of folio_put(). This mismatch between allocation and deallocation methods causes slab allocator corruption. Additionally, the pointer is not reset after freeing, leading to potential use-after-free. The fix applies folio_put() on the error path and nullifies the pointer to prevent UAF by callers.
Affected products
- <UNKNOWN> Linux kernel Multiple stable versions (fix applied across linux-5.x through linux-7.x)
Timeline
- 2026-09-25: disclosed
- 2026-09-21: patched