Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

CVE-2026-98600: Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame()

—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Fixed version: Linux Linux 6.12.112, 6.18.55, 6d91041bb38b97e2feb625123cc0529d7b83a0e1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 6.12.112, 6.18.55, 6d91041bb38b97e2feb625123cc0529d7b83a0e1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame() While rfcomm_recv_frame() verifies that skb->len is at least sizeof(*hdr) + 1 (4 bytes: 3-byte header + 1-byte FCS), an RFCOMM frame with an extended 2-byte length field (!__test_ea(hdr->len)) has a 4-byte header plus a 1-byte FCS (5 bytes minimum, sizeof(*hdr) + 2). When a 4-byte RFCOMM frame with EA == 0 arrives: 1. The initial skb->len < sizeof(*hdr) + 1 check passes (4 < 4 is false). 2. Trimming the FCS byte decrements skb->len to 3. 3. If __check_fcs() succeeds, skb_pull(skb, 4) fails (4 > 3) and returns NULL without advancing skb->data. 4. Because the return value of skb_pull() is ignored, the un-pulled 3-byte struct rfcomm_hdr remains at skb->data and is either queued as application payload via rfcomm_recv_data() or parsed as a multiplexer control command via rfcomm_recv_mcc() on DLCI 0. Fix this by extending the length check in rfcomm_recv_frame() to also require skb->len >= sizeof(*hdr) + 2 when !__test_ea(hdr->len).

Published
Oct 18, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-98600

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 7.2affected
    • fb40eda15122f6b780228639c1ead6820340ff54 and later · before 76876fd26569302d26d91cbe8b75fa8e66cf8969affected · git
    • 3829af5fab5a22405bf1e7d69068c2ec0fce46ca and later · before 97711b964877242933484989224a3c4c5d88a5eeaffected · git
    • b161eacd7fa4a2d765724b5504ac6cc388e48f80 and later · before 7a1781a2f3a9667b3065d402d1f11986a2363e08affected · git
    • 30d1d9f3495463f7c026e4c553127f79b486fcd6 and later · before c25587fa26761e623198b4f47151fe79d09ccde6affected · git
    • 67dc3b40fae71b6b11c71e7ff69bac0758818c05 and later · before 71ccacde407b7d8f0ef48974a0d2524602fd5c44affected · git
    • bbc310caa2b6bf5fe42896ba27da0fbc12e4ac51 and later · before be00deee60044ffa820f9436415caeb665b2cda0affected · git
    • b230e5bf501c5edaf2eb0991cb862ac142031d4b and later · before 9240fc1f2cde5331c61608da21b00394602ca762affected · git
    • b230e5bf501c5edaf2eb0991cb862ac142031d4b and later · before 6d91041bb38b97e2feb625123cc0529d7b83a0e1affected · git
    • 6.12.111 and later · before 6.12.112affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linux-6.12before 6.12.113-1~deb12u16.12.113-1~deb12u1
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.9-17.2.9-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98598Oct 18, 2026 · ipv6: Prevent rt6_insert_exception() for dying fib6_info.
    0Monitor
  • ← EarlierCVE-2026-98599Oct 18, 2026 · bpf: Reject non-negative offsets in stack_slot_obj_get_spi()
    0Monitor
  • Later →CVE-2026-98601Oct 18, 2026 · Bluetooth: btintel_pcie: validate device-supplied DMA indices
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux6.12.112Vendor (CNA)
Linux Linux6.18.55Vendor (CNA)
Linux Linux6d91041bb38b97e2feb625123cc0529d7b83a0e1Vendor (CNA)
Linux Linux71ccacde407b7d8f0ef48974a0d2524602fd5c44Vendor (CNA)
Linux Linux76876fd26569302d26d91cbe8b75fa8e66cf8969Vendor (CNA)
Linux Linux7a1781a2f3a9667b3065d402d1f11986a2363e08Vendor (CNA)
Linux Linux9240fc1f2cde5331c61608da21b00394602ca762Vendor (CNA)
Linux Linux97711b964877242933484989224a3c4c5d88a5eeVendor (CNA)
Linux Linuxbe00deee60044ffa820f9436415caeb665b2cda0Vendor (CNA)
Linux Linuxc25587fa26761e623198b4f47151fe79d09ccde6Vendor (CNA)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 16, 2026+29 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records