CVE-2024-26995
Last modified
CVE-2024-26995 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: Correct the PDO counting in pd_set Off-by-one errors happen because nr_snk_pdo and nr_src_pdo are incorrectly added one. The index of the loop is equal to the number of PDOs to be updated when leaving the loop and it doesn't need to be added one. When doing the power negotiation, TCPM relies on the "nr_snk_pdo" as the size of the local sink PDO array to match the Source capabilities of the partner port. EPSS estimates a 0.24% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: Correct the PDO counting in pd_set Off-by-one errors happen because nr_snk_pdo and nr_src_pdo are incorrectly added one. The index of the loop is equal to the number of PDOs to be updated when leaving the loop and it doesn't need to be added one. When doing the power negotiation, TCPM relies on the "nr_snk_pdo" as the size of the local sink PDO array to match the Source capabilities of the partner port. If the off-by-one overflow occurs, a wrong RDO might be sent and unexpected power transfer might happen such as over voltage or over current (than expected). "nr_src_pdo" is used to set the Rp level when the port is in Source role. It is also the array size of the local Source capabilities when filling up the buffer which will be sent as the Source PDOs (such as in Power Negotiation). If the off-by-one overflow occurs, a wrong Rp level might be set and wrong Source PDOs will be sent to the partner port. This could potentially cause over current or port resets.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.8, < 6.8.8 | — |
| Linux | Linux Kernel | 6.9 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-26995?
How severe is CVE-2024-26995?
How do I fix CVE-2024-26995?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-26989In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-26990In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26991In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26992In the Linux kernel, the following vulnerability has been re…3.3
- CVE-2024-26993In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26994In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26996In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-26997In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26998In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26999In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-2700A vulnerability was found in the quarkus-core component. Qua…7
- CVE-2024-27000In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2024-26995?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
