BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-53208High confidence

Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 29 Jun 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.12% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-53208 · CSAF 2.0 · revision 14 · interimSUSE Product Security TeamCVE-2026-53208
272 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig net/bluetooth/l2cap_core.c:l2cap_sig_channel() accepts BR/EDR signaling packets up to the channel MTU and dispatches each command without enforcing the signaling MTU (MTUsig). A Bluetooth BR/EDR peer within radio range can send a fixed-channel CID 0x0001 packet that is larger than MTUsig and contains many L2CAP_ECHO_REQ commands before pairing. In a real-radio stock-kernel run, one 681-byte signaling packet containing 168 zero-length ECHO_REQ commands made the target transmit 168 ECHO_RSP frames over about 220 ms. Impact: a Bluetooth BR/EDR peer within radio range, before pairing, can force 168 ECHO_RSP frames from one 681-byte fixed-channel signaling packet containing packed ECHO_REQ commands. Define Linux's BR/EDR signaling MTU as the spec minimum of 48 bytes and reject any larger signaling packet with one L2CAP_COMMAND_REJECT_RSP carrying L2CAP_REJ_MTU_EXCEEDED before any command is dispatched. The Bluetooth Core spec wording for MTUExceeded says the reject identifier shall match the first request command in the packet, and that packets containing only responses shall be silently discarded. Linux intentionally deviates from that prescription: silently discarding desynchronizes the peer because the remote stack never learns its responses were dropped, and locating the first request command requires walking command headers past MTUsig, i.e. processing bytes from a packet we have already decided is too large to process. We therefore always emit one reject and use the identifier from the first command header, a single fixed-offset byte read. The unrestricted BR/EDR signaling parser and ECHO_REQ response path both trace to the initial git import; no later introducing commit is available for a Fixes tag.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-39299

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig net/bluetooth/l2cap_core.c:l2cap_sig_channel() accepts BR/EDR signaling packets up to the channel MTU and dispatches each command without enforcing the signaling MTU (MTUsig). A Bluetooth BR/EDR peer within radio range can send a fixed-channel CID 0x0001 packet that is larger than MTUsig and contains many L2CAP_ECHO_REQ commands before pairing. In a real-radio stock-kernel run, one 681-byte signaling packet containing 168 zero-length ECHO_REQ commands made the target transmit 168 ECHO_RSP frames over about 220 ms. Impact: a Bluetooth BR/EDR peer within radio range, before pairing, can force 168 ECHO_RSP frames from one 681-byte fixed-channel signaling packet containing packed ECHO_REQ commands. Define Linux's BR/EDR signaling MTU as the spec minimum of 48 bytes and reject any larger signaling packet with one L2CAP_COMMAND_REJECT_RSP carrying L2CAP_REJ_MTU_EXCEEDED before any command is dispatched. The Bluetooth Core spec wording for MTUExceeded says the reject identifier shall match the first request command in the packet, and that packets containing only responses shall be silently discarded. Linux intentionally deviates from that prescription: silently discarding desynchronizes the peer because the remote stack never learns its responses were dropped, and locating the first request command requires walking command headers past MTUsig, i.e. processing bytes from a packet we have already decided is too large to process. We therefore always emit one reject and use the identifier from the first command header, a single fixed-offset byte read. The unrestricted BR/EDR signaling parser and ECHO_REQ response path both trace to the initial git import; no later introducing commit is available for a Fixes tag.

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig net/bluetooth/l2cap_core.c:l2cap_sig_channel() accepts BR/EDR signaling packets up to the channel MTU and dispatches each command without enforcing the signaling MTU (MTUsig). A Bluetooth BR/EDR peer within radio range can send a fixed-channel CID 0x0001 packet that is larger than MTUsig and contains many L2CAP_ECHO_REQ commands before pairing. In a real-radio stock-kernel run, one 681-byte signaling packet containing 168 zero-length ECHO_REQ commands made the target transmit 168 ECHO_RSP frames over about 220 ms. Impact: a Bluetooth BR/EDR peer within radio range, before pairing, can force 168 ECHO_RSP frames from one 681-byte fixed-channel signaling packet containing packed ECHO_REQ commands. Define Linux's BR/EDR signaling MTU as the spec minimum of 48 bytes and reject any larger signaling packet with one L2CAP_COMMAND_REJECT_RSP carrying L2CAP_REJ_MTU_EXCEEDED before any command is dispatched. The Bluetooth Core spec wording for MTUExceeded says the reject identifier shall match the first request command in the packet, and that packets containing only responses shall be silently discarded. Linux intentionally deviates from that prescription: silently discarding desynchronizes the peer because the remote stack never learns its responses were dropped, and locating the first request command requires walking command headers past MTUsig, i.e. processing bytes from a packet we have already decided is too large to process. We therefore always emit one reject and use the identifier from the first command header, a single fixed-offset byte read. The unrestricted BR/EDR signaling parser and ECHO_REQ response path both trace to the initial git import; no later introducing commit is available for a Fixes tag.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig net/bluetooth/l2cap_core.c:l2cap_sig_channel() accepts BR/EDR signaling packets up to the channel MTU and dispatches each command without enforcing the signaling MTU (MTUsig). A Bluetooth BR/EDR peer within radio range can send a fixed-channel CID 0x0001 packet that is larger than MTUsig and contains many L2CAP_ECHO_REQ commands before pairing. In a real-radio stock-kernel run, one 681-byte signaling packet containing 168 zero-length ECHO_REQ commands made the target transmit 168 ECHO_RSP frames over about 220 ms. Impact: a Bluetooth BR/EDR peer within radio range, before pairing, can force 168 ECHO_RSP frames from one 681-byte fixed-channel signaling packet containing packed ECHO_REQ commands. Define Linux's BR/EDR signaling MTU as the spec minimum of 48 bytes and reject any larger signaling packet with one L2CAP_COMMAND_REJECT_RSP carrying L2CAP_REJ_MTU_EXCEEDED before any command is dispatched. The Bluetooth Core spec wording for MTUExceeded says the reject identifier shall match the first request command in the packet, and that packets containing only responses shall be silently discarded. Linux intentionally deviates from that prescription: silently discarding desynchronizes the peer because the remote stack never learns its responses were dropped, and locating the first request command requires walking command headers past MTUsig, i.e. processing bytes from a packet we have already decided is too large to process. We therefore always emit one reject and use the identifier from the first command header, a single fixed-offset byte read. The unrestricted BR/EDR signaling parser and ECHO_REQ response path both trace to the initial git import; no later introducing commit is available for a Fixes tag.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2077Linux Kernel: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 1 July 2026, published on 1 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53199 Référence CVE CVE-2026-53200 https://www.cve.org/CVERecord?id=CVE-2026-53200 Référence CVE CVE-2026-53201 https://www.cve.org/CVERecord?id=CVE-2026-53201 Référence CVE CVE-2026-53202 https://www.cve.org/CVERecord?id=CVE-2026-53202 Référence CVE CVE-2026-53203 https://www.cve.org/CVERecord?id=CVE-2026-53203 Référence CVE CVE-2026-53204 https://www.cve.org/CVERecord?id=CVE-2026-53204 Référence CVE CVE-2026-53205 https://www.cve.org/CVERecord?id=CVE-2026-53205 Référence CVE CVE-2026-53206 https://www.cve.org/CVERecord?id=CVE-2026-53206 Référence CVE CVE-2026-53207 https://www.cve.org/CVERecord?id=CVE-2026-53207 Référence CVE CVE-2026-53208 https://www.cve.org/CVERecord?id=CVE-2026-53208 Référence CVE CVE-2026-53209 https://www.cve.org/CVERecord?id=CVE-2026-53209 Référence CVE CVE-2026-53210 https://www.cve.org/CVERecord?id=CVE-2026-53210 Référence CVE CVE-2026-53211 https://www.cve.org/CVERecord?id=CVE-2026-53211 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53213 https://www.cve.org/CVERecord?id=CVE-2026-53213 Référence CVE CVE-2026-53214 https://www.cve.org/CVERecord?id=CVE-2026-53214 Référence CVE CVE-2026-53215 https://www.cve.org/CVERecord?id=CVE-2026-53215 Référence CVE CVE-2026-53216 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53199 Référence CVE CVE-2026-53200 https://www.cve.org/CVERecord?id=CVE-2026-53200 Référence CVE CVE-2026-53201 https://www.cve.org/CVERecord?id=CVE-2026-53201 Référence CVE CVE-2026-53202 https://www.cve.org/CVERecord?id=CVE-2026-53202 Référence CVE CVE-2026-53203 https://www.cve.org/CVERecord?id=CVE-2026-53203 Référence CVE CVE-2026-53204 https://www.cve.org/CVERecord?id=CVE-2026-53204 Référence CVE CVE-2026-53205 https://www.cve.org/CVERecord?id=CVE-2026-53205 Référence CVE CVE-2026-53206 https://www.cve.org/CVERecord?id=CVE-2026-53206 Référence CVE CVE-2026-53207 https://www.cve.org/CVERecord?id=CVE-2026-53207 Référence CVE CVE-2026-53208 https://www.cve.org/CVERecord?id=CVE-2026-53208 Référence CVE CVE-2026-53209 https://www.cve.org/CVERecord?id=CVE-2026-53209 Référence CVE CVE-2026-53210 https://www.cve.org/CVERecord?id=CVE-2026-53210 Référence CVE CVE-2026-53211 https://www.cve.org/CVERecord?id=CVE-2026-53211 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53213 https://www.cve.org/CVERecord?id=CVE-2026-53213 Référence CVE CVE-2026-53214 https://www.cve.org/CVERecord?id=CVE-2026-53214 Référence CVE CVE-2026-53215 https://www.cve.org/CVERecord?id=CVE-2026-53215 Référence CVE CVE-2026-53216 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53199 Référence CVE CVE-2026-53200 https://www.cve.org/CVERecord?id=CVE-2026-53200 Référence CVE CVE-2026-53201 https://www.cve.org/CVERecord?id=CVE-2026-53201 Référence CVE CVE-2026-53202 https://www.cve.org/CVERecord?id=CVE-2026-53202 Référence CVE CVE-2026-53203 https://www.cve.org/CVERecord?id=CVE-2026-53203 Référence CVE CVE-2026-53204 https://www.cve.org/CVERecord?id=CVE-2026-53204 Référence CVE CVE-2026-53205 https://www.cve.org/CVERecord?id=CVE-2026-53205 Référence CVE CVE-2026-53206 https://www.cve.org/CVERecord?id=CVE-2026-53206 Référence CVE CVE-2026-53207 https://www.cve.org/CVERecord?id=CVE-2026-53207 Référence CVE CVE-2026-53208 https://www.cve.org/CVERecord?id=CVE-2026-53208 Référence CVE CVE-2026-53209 https://www.cve.org/CVERecord?id=CVE-2026-53209 Référence CVE CVE-2026-53210 https://www.cve.org/CVERecord?id=CVE-2026-53210 Référence CVE CVE-2026-53211 https://www.cve.org/CVERecord?id=CVE-2026-53211 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53213 https://www.cve.org/CVERecord?id=CVE-2026-53213 Référence CVE CVE-2026-53214 https://www.cve.org/CVERecord?id=CVE-2026-53214 Référence CVE CVE-2026-53216 https://www.cve.org/CVERecord?id=CVE-2026-53216 Référence CVE CVE-2026-53217 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53199 Référence CVE CVE-2026-53200 https://www.cve.org/CVERecord?id=CVE-2026-53200 Référence CVE CVE-2026-53201 https://www.cve.org/CVERecord?id=CVE-2026-53201 Référence CVE CVE-2026-53202 https://www.cve.org/CVERecord?id=CVE-2026-53202 Référence CVE CVE-2026-53203 https://www.cve.org/CVERecord?id=CVE-2026-53203 Référence CVE CVE-2026-53204 https://www.cve.org/CVERecord?id=CVE-2026-53204 Référence CVE CVE-2026-53205 https://www.cve.org/CVERecord?id=CVE-2026-53205 Référence CVE CVE-2026-53206 https://www.cve.org/CVERecord?id=CVE-2026-53206 Référence CVE CVE-2026-53207 https://www.cve.org/CVERecord?id=CVE-2026-53207 Référence CVE CVE-2026-53208 https://www.cve.org/CVERecord?id=CVE-2026-53208 Référence CVE CVE-2026-53209 https://www.cve.org/CVERecord?id=CVE-2026-53209 Référence CVE CVE-2026-53210 https://www.cve.org/CVERecord?id=CVE-2026-53210 Référence CVE CVE-2026-53211 https://www.cve.org/CVERecord?id=CVE-2026-53211 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53213 https://www.cve.org/CVERecord?id=CVE-2026-53213 Référence CVE CVE-2026-53214 https://www.cve.org/CVERecord?id=CVE-2026-53214 Référence CVE CVE-2026-53215 https://www.cve.org/CVERecord?id=CVE-2026-53215 Référence CVE CVE-2026-53216 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53191 Référence CVE CVE-2026-53192 https://www.cve.org/CVERecord?id=CVE-2026-53192 Référence CVE CVE-2026-53193 https://www.cve.org/CVERecord?id=CVE-2026-53193 Référence CVE CVE-2026-53195 https://www.cve.org/CVERecord?id=CVE-2026-53195 Référence CVE CVE-2026-53196 https://www.cve.org/CVERecord?id=CVE-2026-53196 Référence CVE CVE-2026-53199 https://www.cve.org/CVERecord?id=CVE-2026-53199 Référence CVE CVE-2026-53202 https://www.cve.org/CVERecord?id=CVE-2026-53202 Référence CVE CVE-2026-53203 https://www.cve.org/CVERecord?id=CVE-2026-53203 Référence CVE CVE-2026-53205 https://www.cve.org/CVERecord?id=CVE-2026-53205 Référence CVE CVE-2026-53208 https://www.cve.org/CVERecord?id=CVE-2026-53208 Référence CVE CVE-2026-53209 https://www.cve.org/CVERecord?id=CVE-2026-53209 Référence CVE CVE-2026-53210 https://www.cve.org/CVERecord?id=CVE-2026-53210 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53213 https://www.cve.org/CVERecord?id=CVE-2026-53213 Référence CVE CVE-2026-53214 https://www.cve.org/CVERecord?id=CVE-2026-53214 Référence CVE CVE-2026-53218 https://www.cve.org/CVERecord?id=CVE-2026-53218 Référence CVE CVE-2026-53221 https://www.cve.org/CVERecord?id=CVE-2026-53221 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1029Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53146 Référence CVE CVE-2026-53147 https://www.cve.org/CVERecord?id=CVE-2026-53147 Référence CVE CVE-2026-53149 https://www.cve.org/CVERecord?id=CVE-2026-53149 Référence CVE CVE-2026-53167 https://www.cve.org/CVERecord?id=CVE-2026-53167 Référence CVE CVE-2026-53176 https://www.cve.org/CVERecord?id=CVE-2026-53176 Référence CVE CVE-2026-53177 https://www.cve.org/CVERecord?id=CVE-2026-53177 Référence CVE CVE-2026-53181 https://www.cve.org/CVERecord?id=CVE-2026-53181 Référence CVE CVE-2026-53186 https://www.cve.org/CVERecord?id=CVE-2026-53186 Référence CVE CVE-2026-53196 https://www.cve.org/CVERecord?id=CVE-2026-53196 Référence CVE CVE-2026-53208 https://www.cve.org/CVERecord?id=CVE-2026-53208 Référence CVE CVE-2026-53213 https://www.cve.org/CVERecord?id=CVE-2026-53213 Référence CVE CVE-2026-53218 https://www.cve.org/CVERecord?id=CVE-2026-53218 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53225 https://www.cve.org/CVERecord?id=CVE-2026-53225 Référence CVE CVE-2026-53227 https://www.cve.org/CVERecord?id=CVE-2026-53227 Référence CVE CVE-2026-53236 https://www.cve.org/CVERecord?id=CVE-2026-53236 Référence CVE CVE-2026-53242 https://www.cve.org/CVERecord?id=CVE-2026-53242 Référence CVE CVE-2026-53245 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0927Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53182 Référence CVE CVE-2026-53186 https://www.cve.org/CVERecord?id=CVE-2026-53186 Référence CVE CVE-2026-53190 https://www.cve.org/CVERecord?id=CVE-2026-53190 Référence CVE CVE-2026-53192 https://www.cve.org/CVERecord?id=CVE-2026-53192 Référence CVE CVE-2026-53194 https://www.cve.org/CVERecord?id=CVE-2026-53194 Référence CVE CVE-2026-53195 https://www.cve.org/CVERecord?id=CVE-2026-53195 Référence CVE CVE-2026-53196 https://www.cve.org/CVERecord?id=CVE-2026-53196 Référence CVE CVE-2026-53202 https://www.cve.org/CVERecord?id=CVE-2026-53202 Référence CVE CVE-2026-53203 https://www.cve.org/CVERecord?id=CVE-2026-53203 Référence CVE CVE-2026-53208 https://www.cve.org/CVERecord?id=CVE-2026-53208 Référence CVE CVE-2026-53209 https://www.cve.org/CVERecord?id=CVE-2026-53209 Référence CVE CVE-2026-53213 https://www.cve.org/CVERecord?id=CVE-2026-53213 Référence CVE CVE-2026-53215 https://www.cve.org/CVERecord?id=CVE-2026-53215 Référence CVE CVE-2026-53216 https://www.cve.org/CVERecord?id=CVE-2026-53216 Référence CVE CVE-2026-53217 https://www.cve.org/CVERecord?id=CVE-2026-53217 Référence CVE CVE-2026-53218 https://www.cve.org/CVERecord?id=CVE-2026-53218 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53225 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0862Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-53184 Référence CVE CVE-2026-53186 https://www.cve.org/CVERecord?id=CVE-2026-53186 Référence CVE CVE-2026-53189 https://www.cve.org/CVERecord?id=CVE-2026-53189 Référence CVE CVE-2026-53194 https://www.cve.org/CVERecord?id=CVE-2026-53194 Référence CVE CVE-2026-53195 https://www.cve.org/CVERecord?id=CVE-2026-53195 Référence CVE CVE-2026-53196 https://www.cve.org/CVERecord?id=CVE-2026-53196 Référence CVE CVE-2026-53198 https://www.cve.org/CVERecord?id=CVE-2026-53198 Référence CVE CVE-2026-53199 https://www.cve.org/CVERecord?id=CVE-2026-53199 Référence CVE CVE-2026-53207 https://www.cve.org/CVERecord?id=CVE-2026-53207 Référence CVE CVE-2026-53208 https://www.cve.org/CVERecord?id=CVE-2026-53208 Référence CVE CVE-2026-53209 https://www.cve.org/CVERecord?id=CVE-2026-53209 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53213 https://www.cve.org/CVERecord?id=CVE-2026-53213 Référence CVE CVE-2026-53215 https://www.cve.org/CVERecord?id=CVE-2026-53215 Référence CVE CVE-2026-53216 https://www.cve.org/CVERecord?id=CVE-2026-53216 Référence CVE CVE-2026-53217 https://www.cve.org/CVERecord?id=CVE-2026-53217 Référence CVE CVE-2026-53218 https://www.cve.org/CVERecord?id=CVE-2026-53218 Référence CVE CVE-2026-53219 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-022343LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、次の脆弱性が修正されました:Bluetooth: L2CAP: MTUsig を超える BR/EDR シグナリングパケットを拒否net/bluetooth/l2cap_core.c:l2cap_sig_channel() は、チャネル MTU までの BR/EDR シグナリングパケットを受け入れ、シグナリング MTU（MTUsig）を強制せずに各コマンドをディスパッチしていました。無線圏内の Bluetooth BR/EDR ピアは、ペアリング前でも、MTUsig を超えるサイズで多数の L2CAP_ECHO_REQ コマンドを詰め込んだ固定チャネル CID 0x0001 のパケットを送信できます。実際の無線環境で標準カーネルを用いた実行では、ゼロ長の ECHO_REQ を 168 個含む 681 バイトのシグナリングパケット 1 個で、約 220 ms の間に対象に 168 個の ECHO_RSP フレームを送信させることができました。影響: 無線圏内の Bluetooth BR/EDR ピアは、ペアリング前でも、ECHO_REQ コマンドを詰め込んだ 681 バイトの固定チャネル・シグナリングパケット 1 個だけで、168 個の ECHO_RSP フレームを強制的に送信させることができます。Linux の BR/EDR シグナリング MTU を仕様最小値の 48 バイトと定義し、いかなるコマンドもディスパッチする前に、L2CAP_REJ_MTU_EXCEEDED を含む L2CAP_COMMAND_REJECT_RSP を 1 件返して、それより大きいシグナリングパケットを拒否します。Bluetooth Core 仕様の MTUExceeded の記述では、拒否の識別子はパケット内の最初の要求コマンドに一致しなければならず、応答のみを含むパケットは黙って破棄するとされています。Linux は意図的にこの規定から逸脱します。黙って破棄すると、リモートスタックは自分の応答が破棄されたことを知り得ず、ピア間の同期が崩れるためです。また、最初の要求コマンドを見つけるには MTUsig を超えてコマンドヘッダをたどる必要があり、すなわち処理対象外と判断した過大パケットのバイトを処理することになります。したがって、常に拒否を 1 件送出し、最初のコマンドヘッダから識別子を用います。これは固定オフセットの 1 バイト読み出しで済みます。制限のない BR/EDR シグナリングパーサと ECHO_REQ 応答経路はいずれも Git の初期取り込みに遡り、Fixes タグに用いるべき導入コミットは存在しません。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 2.6.12, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.143 ≤ 6.6.*, 6.12.94 ≤ 6.12.*, 6.18.36 ≤ 6.18.*, 7.0.13 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 25 Jun 2026 · Last source change 29 Jun 2026, 04:18 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-39299
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-39299↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-53208 · cve.blacktree.nl