NVD / CVE Program· CNA Linux

CVE-2021-46980: usb: typec: ucsi: Retrieve all the PDOs instead of just the first 4

HighCVSS 7.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 28/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.23% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 1f4642b72be79757f050924a9b9673b6a02034bc, 5e9c6f58b01e6fdfbc740390c01f542a35c97e57, a453bfd7ef15fd9d524004d3ca7b05353a302911.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1f4642b72be79757f050924a9b9673b6a02034bc, 5e9c6f58b01e6fdfbc740390c01f542a35c97e57, a453bfd7ef15fd9d524004d3ca7b05353a302911 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: ucsi: Retrieve all the PDOs instead of just the first 4 commit 4dbc6a4ef06d ("usb: typec: ucsi: save power data objects in PD mode") introduced retrieval of the PDOs when connected to a PD-capable source. But only the first 4 PDOs are received since that is the maximum number that can be fetched at a time given the MESSAGE_IN length limitation (16 bytes). However, as per the PD spec a connected source may advertise up to a maximum of 7 PDOs. If such a source is connected it's possible the PPM could have negotiated a power contract with one of the PDOs at index greater than 4, and would be reflected in the request data object's (RDO) object position field. This would result in an out-of-bounds access when the rdo_index() is used to index into the src_pdos array in ucsi_psy_get_voltage_now(). With the help of the UBSAN -fsanitize=array-bounds checker enabled this exact issue is revealed when connecting to a PD source adapter that advertise 5 PDOs and the PPM enters a contract having selected the 5th one. [ 151.545106][ T70] Unexpected kernel BRK exception at EL1 [ 151.545112][ T70] Internal error: BRK handler: f2005512 [#1] PREEMPT SMP ... [ 151.545499][ T70] pc : ucsi_psy_get_prop+0x208/0x20c [ 151.545507][ T70] lr : power_supply_show_property+0xc0/0x328 ... [ 151.545542][ T70] Call trace: [ 151.545544][ T70] ucsi_psy_get_prop+0x208/0x20c [ 151.545546][ T70] power_supply_uevent+0x1a4/0x2f0 [ 151.545550][ T70] dev_uevent+0x200/0x384 [ 151.545555][ T70] kobject_uevent_env+0x1d4/0x7e8 [ 151.545557][ T70] power_supply_changed_work+0x174/0x31c [ 151.545562][ T70] process_one_work+0x244/0x6f0 [ 151.545564][ T70] worker_thread+0x3e0/0xa64 We can resolve this by instead retrieving and storing up to the maximum of 7 PDOs in the con->src_pdos array. This would involve two calls to the GET_PDOS command.

Memory safety

BDU:2025-02855

Published: Feb 28, 2024
Updated: Jun 17, 2026
EPSS: 0.2% · 13th percentile
CWE: CWE-125

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

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.

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.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

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
- 5.8affected
- 4dbc6a4ef06d6a79ff91be6fc2e90f8660031ce0 and later · before e5366bea0277425e1868ba20eeb27c879d5a6e2daffected · git
- 4dbc6a4ef06d6a79ff91be6fc2e90f8660031ce0 and later · before a453bfd7ef15fd9d524004d3ca7b05353a302911affected · git
- 4dbc6a4ef06d6a79ff91be6fc2e90f8660031ce0 and later · before 5e9c6f58b01e6fdfbc740390c01f542a35c97e57affected · git
- 4dbc6a4ef06d6a79ff91be6fc2e90f8660031ce0 and later · before 1f4642b72be79757f050924a9b9673b6a02034bcaffected · git
- before 5.8not affected · semver
- 5.10.38 and later · up to and including 5.10.*not affected · semver
- 5.11.22 and later · up to and including 5.11.*not affected · semver
- 5.12.5 and later · up to and including 5.12.*not affected · semver
- 5.13 and laternot affected · original_commit_for_fix

Affected versions · NVD (4)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel5.8 and later · before 5.10.38
linux linux kernel5.11 and later · before 5.11.22
linux linux kernel5.12 and later · before 5.12.5
linux linux kernel5.13

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 5.10.38-1	5.10.38-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2021-46978Feb 28, 2024 · KVM: nVMX: Always make an attempt to map eVMCS after migration
31Monitor
← EarlierCVE-2021-46979Feb 28, 2024 · iio: core: fix ioctl handlers removal
22Monitor
Later →CVE-2021-46981Feb 28, 2024 · nbd: Fix NULL pointer in flush_workqueue
22Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
Linux Linux	1f4642b72be79757f050924a9b9673b6a02034bc	Vendor (CNA)
Linux Linux	5e9c6f58b01e6fdfbc740390c01f542a35c97e57	Vendor (CNA)
Linux Linux	a453bfd7ef15fd9d524004d3ca7b05353a302911	Vendor (CNA)
Linux Linux	e5366bea0277425e1868ba20eeb27c879d5a6e2d	Vendor (CNA)
debian:linux	5.10.38-1 · Debian:12	Package 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.