CVE-2026-23395 [High] | Security Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ Currently the code attempts to accept requests regardless of the command identifier which may cause multiple requests to be marked as pending (FLAG_DEFER_SETUP) which can cause more than L2CAP_ECRED_MAX_CID(5) to be allocated in l2cap_ecred_rsp_defer causing an overflow. The spec is quite clear that the same identifier shall not be used on subsequent requests: 'Within each signaling channel a different Identifier shall be used for each successive request or indication.' https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Core-62/out/en/host/logical-link-control-and-adaptation-protocol-specification.html#UUID-32a25a06-4aa4-c6c7-77c5-dcfe3682355d So this attempts to check if there are any channels pending with the same identifier and rejects if any are found.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-03-25	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-03-25

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	416baaa9-dc9f-4396-8d5f-8c081fb06d67
8.8	3.1	HIGH	`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

416baaa9-dc9f-4396-8d5f-8c081fb06d67

8.8

3.1

HIGH

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

OS Trackers for CVE-2026-23395

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2026-23395 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6.	https://security-tracker.debian.org/tracker/CVE-2026-23395
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2026-23395
`suse`	medium	CVE-2026-23395 severity moderate: SUSE including 27 source package names (2.1.3-6.144:kernel-default-base-6.4.0-41.1.21.18, 2.1.3-7.127:kernel-default-6.4.0-41.1, …), 72 product×package rows across 17 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/kvm-os-container, … (17 product lines)): Known Not Affected 52, Fixed 20.	https://www.suse.com/security/cve/CVE-2026-23395/
`ubuntu`	medium	CVE-2026-23395 medium priority: Ubuntu including 157 source packages (linux, linux-allwinner-5.19, …), 1256 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): DNE 871, ignored 169, needed 87, released 83, not-affected 46.	https://ubuntu.com/security/CVE-2026-23395

Affected software / configurations for CVE-2026-23395

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.7.1, < 5.10.253	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.203	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.1.167	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.2, < 6.6.130	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.7, < 6.12.78	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.18.20	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.19, < 6.19.10	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	5.7	cpe:2.3:o:linux:linux_kernel:5.7:-::::::
linux	linux_kernel	7.0	cpe:2.3:o:linux:linux_kernel:7.0:rc1::::::
linux	linux_kernel	7.0	cpe:2.3:o:linux:linux_kernel:7.0:rc2::::::
linux	linux_kernel	7.0	cpe:2.3:o:linux:linux_kernel:7.0:rc3::::::
linux	linux_kernel	7.0	cpe:2.3:o:linux:linux_kernel:7.0:rc4::::::
linux	linux_kernel	7.0	cpe:2.3:o:linux:linux_kernel:7.0:rc5::::::
linux	linux_kernel	7.0	cpe:2.3:o:linux:linux_kernel:7.0:rc6::::::
linux	linux_kernel	7.0	cpe:2.3:o:linux:linux_kernel:7.0:rc7::::::

References for CVE-2026-23395

URL	Tags
https://git.kernel.org/stable/c/10a7a702542240d5edb2b39450ac951c59ccd009	Patch
https://git.kernel.org/stable/c/2124d82fd25e1671bb3ceb37998af5aae5903e06	Patch
https://git.kernel.org/stable/c/46e5b71666fb7652082e4e214a3365f4b14f1dc3	Patch
https://git.kernel.org/stable/c/5b3e2052334f2ff6d5200e952f4aa66994d09899	Patch
https://git.kernel.org/stable/c/6b949a6b33cbdf621d9fc6f0c48ac00915dbf514	Patch
https://git.kernel.org/stable/c/8d0d94f8ba5b3a0beec3b0da558b9bea48018117	Patch
https://git.kernel.org/stable/c/e72ee455297b794b852e5cea8d2d7bb17312172a	Patch
https://git.kernel.org/stable/c/fb4a3a26483f3ea2cd21c7a2f7c45d5670600465	Patch

URL

CVE-2026-23395 | Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ

Exploit prediction scoring system (EPSS) score for CVE-2026-23395

Common vulnerability scoring system (CVSS) metrics for CVE-2026-23395

Weakness enumeration for CVE-2026-23395

GitHub Security Advisory for CVE-2026-23395

OS Trackers for CVE-2026-23395

Affected software / configurations for CVE-2026-23395

References for CVE-2026-23395