Linux kernel: Bluetooth: L2CAP: Reject signalling responses in invalid states
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: Reject signalling responses in invalid states
A peer can send configuration messages while an incoming channel is in BT_CONNECT2, before the security or deferred accept gate has completed. A configuration response can then promote the channel to BT_CONNECTED. Configuration responses can also act on channels that are closing, and a late connection response can move a disconnecting channel back to BT_CONFIG.
Accept connection responses only while waiting in BT_CONNECT. Answer configuration requests in BT_CONNECT2, but defer our own request until BT_CONFIG so configuration cannot complete before the gate. Ignore configuration responses outside BT_CONFIG and BT_CONNECTED, and only complete configuration in BT_CONFIG.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99794 (Bluetooth: L2CAP: Reject signalling responses in invalid states), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99794 (entry last updated 2026-11-20):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 2.6.12
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99794 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99794 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/9a63e20fcedef1cb9fd6dc771ee364ca83a36bf2
- https://git.kernel.org/stable/c/1485880c4c91d69533e08769d033f0868c85a539
- https://git.kernel.org/stable/c/c6f3af8470e4f97553a49c48d9336bdd1f927cb0
- https://git.kernel.org/stable/c/6320736af7dcb90da6ee9fd651ecc11c564d45b7
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99794
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99794"}.Affected versions
- Linux LinuxVersion range not reported
- Linux Linux2.6.12
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch5/5No patch listed yet
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 47 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99794 |
| Record | NVD · CVE-2026-99794 |
| Other links 4 | |
| Link | git.kernel.org · stable/c/9a63e20fcedef1cb9fd6dc771ee364ca83a36bf2 |
| Link | git.kernel.org · stable/c/1485880c4c91d69533e08769d033f0868c85a539 |
| Link | git.kernel.org · stable/c/c6f3af8470e4f97553a49c48d9336bdd1f927cb0 |
| Link | git.kernel.org · stable/c/6320736af7dcb90da6ee9fd651ecc11c564d45b7 |
Questions about CVE-2026-99794
Is CVE-2026-99794 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-99794?
Linux: version 2.6.12.
Source: cve.now feed data
Related
- CVE-2026-99795cxl/features: Ensure that count is set before access to ent[] __counted_by()
- CVE-2026-99793Bluetooth: L2CAP: Only accept connection responses to outstanding requests
- CVE-2026-99792smb/server: prevent file publication after tree disconnect
- CVE-2026-99791xfs: improve dirent bounds checking in scrub and repair
- CVE-2026-99790NFSD: stop registering with rpcbind after a failure in listener_set
- CVE-2026-99789block: restore the iterator when rejecting a misaligned bio
No corrections so far. Something wrong on this page? Report an error.