CVE-2021-46980: usb: typec: ucsi: Retrieve all the PDOs instead of just the first 4
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.
Security readout for executives and security teams
Plain-English summary
CVE-2021-46980 is a Linux kernel USB Type-C power delivery bug. Certain PD-capable chargers can advertise more power profiles than the driver stored, causing an out-of-bounds kernel access and possible crash when the negotiated profile is beyond the first four.
Executive priority
Treat as a targeted stability and availability risk, not a confirmed remote compromise issue. Patch through normal kernel maintenance, with higher priority for devices exposed to untrusted USB-C chargers or accessories.
Technical view
The UCSI driver retrieved only four source PDOs despite USB PD allowing up to seven. If the platform policy manager negotiated a contract using a later PDO, rdo_index() could index past src_pdos in ucsi_psy_get_voltage_now(), observed by UBSAN as a kernel BRK exception.
Likely exposure
Linux systems using affected kernel versions with USB Type-C UCSI support and connected to PD sources advertising five or more PDOs are the relevant exposure set.
Exploitation context
The source describes a crash reproduced by connecting a PD adapter advertising five PDOs. There is no KEV listing and no provided evidence of active exploitation.
Researcher notes
Evidence supports an out-of-bounds read/access path in the UCSI power supply property flow. The provided material does not include CVSS, CWE, exploit publication, or broader impact beyond crash behavior observed with UBSAN.
Mitigation direction
Update to a Linux stable kernel containing the referenced UCSI fix.
Confirm vendor or distribution kernel advisories for backported fixes.
Prioritize laptops, tablets, embedded devices, and servers with exposed USB-C PD ports.
Restrict untrusted physical access to USB-C PD ports where patching is delayed.
Validation and detection
Inventory Linux kernel versions on systems with USB Type-C UCSI support.
Check whether deployed kernels include one of the referenced stable commits or a vendor backport.
Review crash logs for ucsi_psy_get_prop or UBSAN array-bounds reports.
Validate distribution advisories before declaring older vendor kernels unaffected.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-46980 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.