Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80889: can: isotp: fix timer drain order, wakeup handling and tx_gen ordering

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Fixed version: Linux Linux 050f010f920da17c1044a4f174766ad553e770b6, 10be509fa8fd95d1e47d40d1f68b0b26dfe9d572, 2753722612d8824d3910096f93059f669009b0f0.

Low priority for now. Upgrade to Linux Linux 050f010f920da17c1044a4f174766ad553e770b6, 10be509fa8fd95d1e47d40d1f68b0b26dfe9d572, 2753722612d8824d3910096f93059f669009b0f0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix timer drain order, wakeup handling and tx_gen ordering This patch is a follow-up to commit cf070fe33bfb ("can: isotp: serialize TX state transitions under so->rx_lock") which addresses following sashiko-bot findings: - isotp_sendmsg(): drain so->txfrtimer first so a stale callback can't re-arm echotimer after the claim - isotp_release(): wake so->wait after forcing ISOTP_SHUTDOWN so a sleeping sendmsg() claim isn't stranded - isotp_sendmsg(): have both wait_event_interruptible() calls in isotp_sendmsg() also wake on ISOTP_SHUTDOWN and do not return claim to IDLE to avoid corrupting a concurrent isotp_release() process. - isotp_sendmsg(): handle potential claim of a new transfer when the wait_event_interruptible() call returns in CAN_ISOTP_WAIT_TX_DONE mode. Don't touch timers and states of the new transfer if a new thread incremented so->tx_gen before getting the lock at err_event_drop. - isotp_sendmsg(): handle a stuck can_send() and omit timer and state changes if a new transfer was claimed. wait_tx_done() returns the error recorded in so->tx_result[], tagged with the caller's own generation. - isotp_tx_timeout(): on a claimed timeout, record the ECOMM error for the timed-out transfer's own generation in so->tx_result[]; sk->sk_err is raised unconditionally, same as every other error path here. - isotp_tx_gen_done()/isotp_tx_timeout(): always read tx.state (acquire) before tx_gen - the reverse order let a weakly ordered CPU pair a fresh tx.state with a stale tx_gen/tx_result slot. - isotp_sendmsg(): wait_tx_done: drain sk_err via sock_error() once we have read the result from so->tx_result[], so an already-reported error doesn't stay latched for a later poll()/SO_ERROR. Also align the remaining lock-free so->tx.state/rx.state/cfecho accesses and use skb->hash as unique loopback echo frame indicator.

—No exploit Fix available
Published
Sep 4, 2026
Updated
Sep 4, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-80889

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • bbedeb67a9a684f2fb78c55bd3662c400526715e and later · before 8acab9fc66d6f426c36968c91a979f70784945a7affected · git
    • 377a8f500704da42ed86a4541ed930e9dcfdb2ea and later · before af7e25c649ed68cbad07f8185af0f31b892cbf29affected · git
    • 6da8119e8dd542194103139812d1a4b7dcd1aedd and later · before 2753722612d8824d3910096f93059f669009b0f0affected · git
    • 0b05eca9589f609e2491b528dccf683168a4cda8 and later · before bf5c4a8b24acb12739ebb9aea5510b007e4f5239affected · git
    • a7d90e7b5e75d7406c889fe36e9a61ee364a00cb and later · before deca7746b57d982cd4f0301f4443f56780c4a048affected · git
    • 37beb16e08cae94cc05840c7274225e3b0b38ae7 and later · before 10be509fa8fd95d1e47d40d1f68b0b26dfe9d572affected · git
    • 4f1fdf1a1c317bcac0c6b6c8e12642c9983de1ca and later · before 35c62ac98d06669aa3f0f38b7829eaca929a611eaffected · git
    • cf070fe33bfbd1a4c21236078fadb35dd223a157 and later · before 050f010f920da17c1044a4f174766ad553e770b6affected · git
    • 5.10.265 and later · before 5.10.267affected · semver
    • 5.15.216 and later · before 5.15.218affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linux-6.12before 6.12.107-1~deb12u16.12.107-1~deb12u1
Debian:13linuxbefore 6.12.105-16.12.105-1
Debian:14linuxbefore 7.1.8-17.1.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-80887Sep 4, 2026 · drm/vmwgfx: use check_add_overflow for shader size+offset bound
    0Monitor
  • ← EarlierCVE-2026-80888Sep 4, 2026 · drm/vmwgfx: drop dma_buf reference on foreign-fd prime import
    0Monitor
  • Later →CVE-2026-80890Sep 4, 2026 · sctp: reject stale cookies with mismatched verification tags
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux050f010f920da17c1044a4f174766ad553e770b6Vendor (CNA)
Linux Linux10be509fa8fd95d1e47d40d1f68b0b26dfe9d572Vendor (CNA)
Linux Linux2753722612d8824d3910096f93059f669009b0f0Vendor (CNA)
Linux Linux35c62ac98d06669aa3f0f38b7829eaca929a611eVendor (CNA)
Linux Linux5.10.267Vendor (CNA)
Linux Linux5.15.218Vendor (CNA)
Linux Linux6.1.185Vendor (CNA)
Linux Linux6.12.103Vendor (CNA)
Linux Linux6.18.44Vendor (CNA)
Linux Linux6.6.151Vendor (CNA)
Linux Linux7.1.8Vendor (CNA)
Linux Linux8acab9fc66d6f426c36968c91a979f70784945a7Vendor (CNA)
Linux Linuxaf7e25c649ed68cbad07f8185af0f31b892cbf29Vendor (CNA)
Linux Linuxbf5c4a8b24acb12739ebb9aea5510b007e4f5239Vendor (CNA)
Linux Linuxdeca7746b57d982cd4f0301f4443f56780c4a048Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
debian:linux6.12.105-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.107-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records