CVE-2026-90370
What it is
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7996: bound TLV walk in mt7996_mcu_get_chip_config The response TLV loop advanced by tlv->len without a minimum, so a theoretical firmware response containing a zero-length TLV could spin forever, hanging the CPU during device probe. The u32 payload was also read without bounds checking. Reject a short fixed field, stop on a TLV whose length underruns the header or overruns the skb.
At a glance
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Received
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-90370.md and follow it. Check whether this project is affected by CVE-2026-90370. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- https://git.kernel.org/stable/c/3106f62809d45c1e6aadfad1f4d7c3f74cd53a96
- https://git.kernel.org/stable/c/39aa6b853b6d69dd1fee3507efdb3c277b7c53e6
- https://git.kernel.org/stable/c/44af52467e72094351a362bf69effd52f1d9c186
- https://git.kernel.org/stable/c/93eaddfdd35aa6bfe570c087db4e97fb9d8a791a
- https://git.kernel.org/stable/c/d0bb2189ade617e624f3c8f444ebb05f59bb2524