Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-54299: usb: typec: bus: verify partner exists in typec_altmode_attention

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.20% (FIRST EPSS).
  • Fixed version: Linux Linux 0ad6bad31da692f8d7acacab07eabe7586239ae0, 0d3b5fe47938e9c451466845304a2bd74e967a80, 1101867a1711c27d8bbe0e83136bec47f8c1ca2a.

Low priority for now. Upgrade to Linux Linux 0ad6bad31da692f8d7acacab07eabe7586239ae0, 0d3b5fe47938e9c451466845304a2bd74e967a80, 1101867a1711c27d8bbe0e83136bec47f8c1ca2a 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: usb: typec: bus: verify partner exists in typec_altmode_attention Some usb hubs will negotiate DisplayPort Alt mode with the device but will then negotiate a data role swap after entering the alt mode. The data role swap causes the device to unregister all alt modes, however the usb hub will still send Attention messages even after failing to reregister the Alt Mode. type_altmode_attention currently does not verify whether or not a device's altmode partner exists, which results in a NULL pointer error when dereferencing the typec_altmode and typec_altmode_ops belonging to the altmode partner. Verify the presence of a device's altmode partner before sending the Attention message to the Alt Mode driver.

—No exploit Fix available
Published
Dec 30, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 10th 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.2%

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-2023-54299

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

    • 4.19affected
    • 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 and later · before 5f71716772b88cbe0e1788f6a38d7871aff2120baffected · git
    • 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 and later · before 38e1f2ee82bacbbfded8f1c06794a443d038d054affected · git
    • 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 and later · before 0ad6bad31da692f8d7acacab07eabe7586239ae0affected · git
    • 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 and later · before 0d3b5fe47938e9c451466845304a2bd74e967a80affected · git
    • 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 and later · before d49547950bf7f3480d6ca05fe055978e5f0d9e5baffected · git
    • 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 and later · before 1101867a1711c27d8bbe0e83136bec47f8c1ca2aaffected · git
    • 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 and later · before f23643306430f86e2f413ee2b986e0773e79da31affected · git
    • before 4.19not affected · semver
    • 5.4.257 and later · up to and including 5.4.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.55-16.1.55-1
Debian:13linuxbefore 6.5.3-16.5.3-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-2023-54297Dec 30, 2025 · btrfs: zoned: fix memory leak after finding block group with super blocks
    0Monitor
  • ← EarlierCVE-2023-54298Dec 30, 2025 · thermal: intel: quark_dts: fix error pointer dereference
    0Monitor
  • Later →CVE-2023-54300Dec 30, 2025 · wifi: ath9k: avoid referencing uninit memory in ath9k_wmi_ctrl_rx
    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 Linux0ad6bad31da692f8d7acacab07eabe7586239ae0Vendor (CNA)
Linux Linux0d3b5fe47938e9c451466845304a2bd74e967a80Vendor (CNA)
Linux Linux1101867a1711c27d8bbe0e83136bec47f8c1ca2aVendor (CNA)
Linux Linux38e1f2ee82bacbbfded8f1c06794a443d038d054Vendor (CNA)
Linux Linux5f71716772b88cbe0e1788f6a38d7871aff2120bVendor (CNA)
Linux Linuxd49547950bf7f3480d6ca05fe055978e5f0d9e5bVendor (CNA)
Linux Linuxf23643306430f86e2f413ee2b986e0773e79da31Vendor (CNA)
debian:linux6.1.55-1 · 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.

No history yet (it accumulates with the daily EPSS job).

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 (6 more)

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

All records