Also known asEUVD-2026-45721 (ENISA EUVD) · GHSA-jg7r-p8w6-9pmq (GitHub Security Advisories)Source: ENISA EUVD
A fix is available — apply it.
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: fix chan ref leak in l2cap_chan_timeout() on !conn
__set_chan_timer() takes a l2cap_chan reference via l2cap_chan_hold() before scheduling the delayed work. The normal path in l2cap_chan_timeout() drops this reference with l2cap_chan_put() at the end, but the early return when chan->conn is NULL skips the put, leaking the reference.
Add the missing l2cap_chan_put() before the early return.
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
July 19, 2026
July 27, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | 5.10.103-1 ... 5.10.92-2 (54 versions) |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | 6.1.106-1 ... 6.1.99-1 (53 versions) |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | 6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions) |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | 6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions) |
| — |
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Linux kernel vulnerabilities
Linux kernel (Azure) vulnerabilities
Linux kernel vulnerabilities
Linux kernel (NVIDIA) vulnerabilities
Linux kernel (NVIDIA BaseOS) vulnerabilities
Linux kernel (GCP) vulnerabilities
Linux kernel (Azure) vulnerabilities
Linux kernel (Oracle) vulnerabilities
Linux kernel (NVIDIA Tegra) vulnerabilities
Linux kernel vulnerabilities
Linux kernel (NVIDIA) vulnerabilities
Linux kernel (GCP) vulnerabilities
Linux kernel (GCP) vulnerabilities
Linux kernel (Oracle) vulnerabilities
Linux kernel vulnerabilities
Linux kernel vulnerabilities
Linux kernel (Azure) vulnerabilities
Linux kernel (GCP) vulnerabilities
Linux kernel (GCP) vulnerabilities
Linux kernel (IBM) vulnerabilities
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 145 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 45 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63948
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.