CVE-2026-45866

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

serial: caif: fix use-after-free in caif_serial ldisc_close()

There is a use-after-free bug in caif_serial where handle_tx() may access ser->tty after the tty has been freed.

The race condition occurs between ldisc_close() and packet transmission:

CPU 0 (close) CPU 1 (xmit) ------------- ------------ ldisc_close() tty_kref_put(ser->tty) [tty may be freed here] <-- race window --> caif_xmit() handle_tx() tty = ser->tty // dangling ptr tty->ops->write() // UAF! schedule_work() ser_release() unregister_netdevice()

The root cause is that tty_kref_put() is called in ldisc_close() while the network device is still active and can receive packets.

Since ser and tty have a 1:1 binding relationship with consistent lifecycles (ser is allocated in ldisc_open and freed in ser_release via unregister_netdevice, and each ser binds exactly one tty), we can safely defer the tty reference release to ser_release() where the network device is unregistered.

Fix this by moving tty_kref_put() from ldisc_close() to ser_release(), after unregister_netdevice(). This ensures the tty reference is held as long as the network device exists, preventing the UAF.

Note: We save ser->tty before unregister_netdevice() because ser is embedded in netdev's private data and will be freed along with netdev (needs_free_netdev = true).

How to reproduce: Add mdelay(500) at the beginning of ldisc_close() to widen the race window, then run the reproducer program [1].

Note: There is a separate deadloop issue in handle_tx() when using PORT_UNKNOWN serial ports (e.g., /dev/ttyS3 in QEMU without proper serial backend). This deadloop exists even without this patch, and is likely caused by inconsistency between uart_write_room() and uart_write() in serial core. It has been addressed in a separate patch [2].

KASAN report:

================================================================== BUG: KASAN: slab-use-after-free in handle_tx+0x5d1/0x620 Read of size 1 at addr ffff8881131e1490 by task caif_uaf_trigge/9929

Call Trace: dump_stack_lvl+0x10e/0x1f0 print_report+0xd0/0x630 kasan_report+0xe4/0x120 handle_tx+0x5d1/0x620 dev_hard_start_xmit+0x9d/0x6c0 __dev_queue_xmit+0x6e2/0x4410 packet_xmit+0x243/0x360 packet_sendmsg+0x26cf/0x5500 __sys_sendto+0x4a3/0x520 __x64_sys_sendto+0xe0/0x1c0 do_syscall_64+0xc9/0xf80 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f615df2c0d7

Allocated by task 9930:

Freed by task 64:

Last potentially related work creation:

The buggy address belongs to the object at ffff8881131e1000 which belongs to the cache kmalloc-cg-2k of size 2048 The buggy address is located 1168 bytes inside of freed 2048-byte region [ffff8881131e1000, ffff8881131e1800)

The buggy address belongs to the physical page: page_owner tracks the page as allocated page last free pid 9778 tgid 9778 stack trace:

Memory state around the buggy address: ffff8881131e1380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff8881131e1400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb >ffff8881131e1480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff8881131e1500: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff8881131e1580: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ================================================================== [1]: https://gist.github.com/mrpre/f683f244544f7b11e7fa87df9e6c2eeb [2]: https://lore.kernel.org/linux-serial/[email protected]/T/#u

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

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

Published

May 27, 2026

Last Modified

June 25, 2026

Advisory Details (8)

Auto-updated Jun 25, 2026
Patch available.
Web page

serial: caif: fix use-after-free in caif_serial ldisc_close() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d3c75db4e0460641dbcd274b40867e252d801da1
Web page

serial: caif: fix use-after-free in caif_serial ldisc_close() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c8c197aaa56b25a2d54f3aa07e27e228d6c08546
Web page

serial: caif: fix use-after-free in caif_serial ldisc_close() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5e266ba8d330d3b8e5bc198f238cd8901826cfa1
Web page

serial: caif: fix use-after-free in caif_serial ldisc_close() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52731ef4438155cea782fac74e547a327ab9e7c5
Web page

serial: caif: fix use-after-free in caif_serial ldisc_close() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e63d6f68544ae5269ac9735ae5b69b59b5b8725
Web page

serial: caif: fix use-after-free in caif_serial ldisc_close() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40962f2bf8cdba63af23aec95ad3f49b689e58e2
Web page

serial: caif: fix use-after-free in caif_serial ldisc_close() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/331e2b7051635780edea248dd08ae2026c126f4a
Web page

serial: caif: fix use-after-free in caif_serial ldisc_close() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/308e7e4d0a846359685f40aade023aee7b27284c

Vendor Advisories for CVE-2026-45866(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(25)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-10-17ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-10-17ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-10-17ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-10-17ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1063.71~22.04.1) @ jammy2026-10-17ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-17ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-10-17ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-10-17ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-17ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-10-17ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-10-17ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-10-17ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-17ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-10-17ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-10-17ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-10-17ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-10-17ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-10-17ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-10-17ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-10-17ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-10-17ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-10-17ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-17ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-10-17ubuntu
linuxKernel @ 5.10.252 (fixes >=3.11.0)—osv

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)
  • every version up to 5.10.257-1: fixed in 5.10.257-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (104 versions)
  • every version up to 6.18.14-1: fixed in 6.18.14-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(24)

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.

Data Freshness Timeline

(refreshed 11× in last 7d / 33× in last 30d)

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 258 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 158 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-10-18 03:37 UTCEG score recompute
  5. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-17 13:33 UTCEG score recompute
  7. 2026-10-17 13:33 UTCVendor advisory
  8. 2026-10-17 13:32 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-12 16:03 UTCEG score recompute
  15. 2026-10-11 19:46 UTCEG score recompute
  16. 2026-10-11 17:00 UTCEG score recompute
  17. 2026-10-11 14:25 UTCEG score recompute
  18. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 75 more
  1. 2026-10-03 18:51 UTCOSV refresh
  2. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-09-14 09:16 UTCEG score recompute
  14. 2026-09-14 09:16 UTCVendor advisory
  15. 2026-09-14 09:16 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-09-13 04:09 UTCOSV refresh
  18. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  26. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  27. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  28. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  29. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  30. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  31. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  32. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  33. 2026-08-25 05:51 UTCEG score recompute
  34. 2026-08-25 05:51 UTCVendor advisory
  35. 2026-08-25 05:51 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8
  36. 2026-08-23 15:37 UTCEG score recompute
  37. 2026-08-23 15:37 UTCVendor advisory
  38. 2026-08-23 15:37 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8
  39. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  40. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-08-21 21:00 UTCEG score recompute
  42. 2026-08-21 21:00 UTCVendor advisory
  43. 2026-08-21 20:59 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-08-20 17:46 UTCEG score recompute
  46. 2026-08-20 17:46 UTCVendor advisory
  47. 2026-08-20 17:45 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  49. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  50. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  51. 2026-08-17 09:22 UTCVendor advisory
  52. 2026-08-17 09:22 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8
  53. 2026-08-16 16:27 UTCEG score recompute
  54. 2026-08-16 16:27 UTCVendor advisory
  55. 2026-08-16 16:27 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8
  56. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  57. 2026-08-16 02:55 UTCEG score recompute
  58. 2026-08-16 02:55 UTCVendor advisory
  59. 2026-08-16 02:55 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  61. 2026-08-15 03:25 UTCEG score recompute
  62. 2026-08-15 03:25 UTCVendor advisory
  63. 2026-08-15 03:25 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8
  64. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  65. 2026-08-14 14:30 UTCVendor advisory
  66. 2026-08-14 14:30 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-08-14 01:35 UTCEG score recompute
  68. 2026-08-14 01:35 UTCVendor advisory
  69. 2026-08-14 01:35 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  71. 2026-08-13 11:25 UTCVendor advisory
  72. 2026-08-13 11:25 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8
  73. 2026-08-12 22:31 UTCEG score recompute
  74. 2026-08-12 22:31 UTCVendor advisory
  75. 2026-08-12 22:31 UTCGHSA enrichmentGHSA-9834-966g-q77h · GitHub severity HIGH · GitHub CVSS 7.8

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-45866?
CVE-2026-45866 is a high-severity vulnerability; its CVE record was published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: serial: caif: fix use-after-free in caifserial ldiscclose() There is a use-after-free bug in caifserial where handletx() may access ser->tty after the tty has been freed. The race condition occurs between ldisc_close() and packet…
When was the CVE record for CVE-2026-45866 published?
The CVE record for CVE-2026-45866 was published on May 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 25, 2026; the record at its source may have been updated since.
Is CVE-2026-45866 actively exploited?
CVE-2026-45866 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45866?
CVE-2026-45866 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-45866?
A fix for CVE-2026-45866 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45866 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45866

Explore →

Is Your Infrastructure Affected by CVE-2026-45866?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs