cve.bz

CVE-2026-98524 linux linux

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: rds: ib: Clear the sg list when mapping an MR fails rds_ib_map_frmr() stores the caller's scatterlist in the MR before DMA mapping and registration can fail. On failure, __rds_rdma_map() unpins the pages and frees the scatterlist, but rds_ib_free_frmr() can still return the MR to the pool with the stale pointer set. This leaves the pool with a dangling scatterlist and can lead to local privilege escalation. KASAN detects the resulting use-after-free when the MR is later torn down: BUG: KASAN: slab-use-after-free in __rds_ib_teardown_mr Read of size 8 Call Trace: __rds_ib_teardown_mr rds_ib_unreg_frmr rds_ib_flush_mr_pool rds_ib_flush_mrs rds_free_mr rds_setsockopt Store the scatterlist in the MR only after DMA mapping succeeds. If DMA mapping fails, return directly while the MR fields remain clear; the caller keeps ownership of the scatterlist and its pinned pages. If a later registration step fails, unmap the scatterlist and clear the MR fields before returning.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.271
  • Linux Linux: fixed in 5.15.222
  • Linux Linux: fixed in 6.1.189
  • Linux Linux: fixed in 6.6.158
  • Linux Linux: fixed in 6.12.112
  • Linux Linux: fixed in 6.18.55
  • Linux Linux: fixed in 7.2.9
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-98524 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98524?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98524?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-98524 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-98524

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-98524](https://cve.bz/cve/badge/CVE-2026-98524.svg)](https://cve.bz/cve/CVE-2026-98524)

HTML:

<a href="https://cve.bz/cve/CVE-2026-98524"><img src="https://cve.bz/cve/badge/CVE-2026-98524.svg" alt="CVE-2026-98524"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux4.6 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.271
Linux5.155.15.222
Linux6.16.1.189
Linux6.66.6.158
Linux6.126.12.112
Linux6.186.18.55
Linux7.27.2.9
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.190-1DEBIAN-CVE-2026-98524
Debian12linux-6.126.12.113-1~deb12u1DEBIAN-CVE-2026-98524
Debian13linux6.12.113-1DEBIAN-CVE-2026-98524
Debian14linux7.2.9-1DEBIAN-CVE-2026-98524
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-98524
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-98524
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-98524
Ubuntu22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-98524 USN-8961-1
Ubuntu22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-98524 USN-8961-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-98524 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-98524 USN-8961-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-98524 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-98524
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-98524 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-98524 USN-8961-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-98524 USN-9024-1
82 more for Ubuntu in the JSON and on Ubuntu's page.
Azure Linux3kernel6.6.159.1-1AZL-109403
Alpaquita23linux-lts6.1.189-r0BELL-CVE-2026-98524
Alpaquita25linux-lts6.12.112-r0BELL-CVE-2026-98524
Alpaquitastreamlinux-lts6.18.55-r0BELL-CVE-2026-98524

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A use after free in the RDS IB Fastreg MR error path occurs because rds_ib_map_frmr can retain a caller owned scatterlist pointer when DMA mapping fails. The caller can then unpin the pages and free the scatterlist while the MR is returned to the pool with the stale pointer still present. A later MR teardown or pool flush can pass the dangling scatterlist to __rds_ib_teardown_mr, and KASAN confirms a slab use after free read in this path. For the CVSS the PR:L reflects that a local user or process must access the RDS RDMA interface and trigger MR registration and cleanup operations. AC:H reflects the additional requirement to reach the DMA mapping failure path and later reuse or tear down the affected pooled MR. The issue is not directly network reachable based on the demonstrated call path even though RDS is a network subsystem. Impact is at least a local denial of service via kernel crash and in the worst case may allow high confidentiality and integrity impact through use after free exploitation and local privilege escalation.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-10-20) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to disable or restrict the RDS protocol and prevent unprivileged local users from creating RDS sockets or invoking rds_setsockopt on InfiniBand-enabled Linux systems: upgrade to the fixed release, which store the scatterlist in the MR only after DMA mapping succeeds, and unmap and clear MR fields if registration fails, closing RDS setsockopt calls triggering InfiniBand memory region mapping failures. Until patched, this is only a concern on Linux systems with local unprivileged user access permitting the creation of RDS sockets and invocation of rds_setsockopt — Non-Linux operating systems are unaffected — so Blacklist the rds and rds_ib kernel modules or restrict local unprivileged user permissions to open RDS sockets and execute rds_setsockopt operations. As a compensating measure, Deploy runtime memory error detection like KASAN to detect slab use-after-free conditions when the dangling scatterlist pointer is dereferenced during memory region teardown, Enable SLAB freelist randomization and pointer integrity verification to hinder exploitation of kernel slab memory corruption, Enforce SELinux in enforcing mode to restrict socket operations and confine post-exploitation actions of compromised processes, Deploy eBPF runtime security monitoring with Falco to detect anomalous kernel-level behavior or privilege escalation attempts via RDS setsockopt calls, Enable SMEP and SMAP to prevent the kernel from executing userspace code or directly accessing userspace data during memory corruption exploitation, and Enable kernel Control Flow Integrity and shadow call stack validation on indirect call targets to prevent control-flow hijacking. These controls limit blast radius and contain exploitation, but they do not fix the underlying slab use-after-free defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-98524.

References

Check your stackJSON