Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43458serial: caif: hold tty->link reference in ldisc_open and ser_release

Description

In the Linux kernel, the following vulnerability has been resolved: serial: caif: hold tty->link reference in ldisc_open and ser_release A reproducer triggers a KASAN slab-use-after-free in pty_write_room() when caif_serial's TX path calls tty_write_room(). The faulting access is on tty->link->port. Hold an extra kref on tty->link for the lifetime of the caif_serial line discipline: get it in ldisc_open() and drop it in ser_release(), and also drop it on the ldisc_open() error path. With this change applied, the reproducer no longer triggers the UAF in my testing.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 3 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43458, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected e31d5a05948e4478ba8396063d1e1f39880928e2 – < 23a3ac2e2262a291498567418227b99e1f3606b1
    • affected e31d5a05948e4478ba8396063d1e1f39880928e2 – < 52135420e9f75853ea0c6cea7b736e3e98495f7d
    • affected e31d5a05948e4478ba8396063d1e1f39880928e2 – < ca2ceba983bb23ea0202c2882d963253416654a3
    • affected e31d5a05948e4478ba8396063d1e1f39880928e2 – < 8460187b4852fd00bd1c76394358053f3fa4d089
    • affected e31d5a05948e4478ba8396063d1e1f39880928e2 – < 27e43356d0defb9fc7fa25265219a3ffeb7b3e98
    • affected e31d5a05948e4478ba8396063d1e1f39880928e2 – < 35b58d3bc716ebb9ebd10fe1cac8c1177242511c
    • affected e31d5a05948e4478ba8396063d1e1f39880928e2 – < 97a0bb491cae39478c6225381f14e9ac67b7bba7
    • affected e31d5a05948e4478ba8396063d1e1f39880928e2 – < 288598d80a068a0e9281de35bcb4ce495f189e2a
  • Linux · Linux

    • affected 2.6.35
    • unaffected < 2.6.35
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.78 – ≤ 6.12.*
    • unaffected 6.18.19 – ≤ 6.18.*
    • unaffected 6.19.9 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43458 badge
[![CVE-2026-43458](https://cveledger.app/badge/CVE-2026-43458.svg)](https://cveledger.app/cve/CVE-2026-43458)

Record last updated .