CVE-2026-98738 linux linux
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
- EPSS
- 0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 6th 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 6.6.160
- Linux Linux: fixed in 6.12.113
- Linux Linux: fixed in 6.18.56
- Linux Linux: fixed in 7.2.10
- Linux Linux: fixed in 7.3
- Debian, Ubuntu, Azure Linux, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-98738 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98738?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98738?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-98738 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.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 3.19 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.6 | 6.6.160 |
| Linux | 6.12 | 6.12.113 |
| Linux | 6.18 | 6.18.56 |
| Linux | 7.2 | 7.2.10 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | no fix listed | DEBIAN-CVE-2026-98738 |
| Debian | 12 | linux-6.12 | 6.12.113-1~deb12u1 | DEBIAN-CVE-2026-98738 |
| Debian | 13 | linux | 6.12.113-1 | DEBIAN-CVE-2026-98738 |
| Debian | 14 | linux | 7.2.10-1 | DEBIAN-CVE-2026-98738 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-98738 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-98738 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-98738 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 48 more | no fix listed | UBUNTU-CVE-2026-98738 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-98738 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-98738 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-98738 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-98738 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-hwe-6.8 | 6.8.0-149.149~22.04.1 | UBUNTU-CVE-2026-98738 USN-9066-1 |
| Ubuntu | 22.04:LTS | linux-ibm-6.8 | 6.8.0-1069.70~22.04.1 | UBUNTU-CVE-2026-98738 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-149.149.1~22.04.1 | UBUNTU-CVE-2026-98738 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-oracle-6.8 | 6.8.0-1067.71~22.04.1 | UBUNTU-CVE-2026-98738 USN-9025-1 |
| 50 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Azure Linux | 3 | kernel | 6.6.161.1-1 | AZL-108674 |
| Alpaquita | 23 | linux-lts | no fix listed | BELL-CVE-2026-98738 |
| Alpaquita | 25 | linux-lts | 6.12.115-r0 | BELL-CVE-2026-98738 |
| Alpaquita | stream | linux-lts | 6.18.58-r0 | BELL-CVE-2026-98738 |
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.
A race in Bluetooth SMP remote OOB handling allows build_pairing_cmd to retain and read an oob_data entry after a concurrent management command removes and frees it. KASAN confirms a slab use-after-free while the receive path reads the present flag or copies remote random and confirmation values. A Bluetooth peer within radio range can exercise the SMP receive path, but reliable triggering also depends on a concurrent remote OOB removal or update and therefore has high attack complexity. For the CVSS the PR:N value is used for the paranoid adjacent attack scenario because the peer does not need an account or privileges on the target when a legitimate local Bluetooth service performs the concurrent removal. Impact is at least denial of service through a kernel crash and may include confidentiality or integrity impact if reclaimed slab contents are consumed as pairing data.
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred |
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-98738.
References
- https://git.kernel.org/stable/c/1e11412a1b9854a89d044576d616675b16141d87
- https://git.kernel.org/stable/c/81a2345f1984f0b36d3226571bc196316a01b648
- https://git.kernel.org/stable/c/889c61e3d0f1091a958e4b2a24b20bab23d915c4
- https://git.kernel.org/stable/c/94afa17d6bfd5c1d367c56c8b63df5f695380861
- https://git.kernel.org/stable/c/df5162eeb10e69fe0c2349503882c4a09077f001