CDC-NCM: avoid overflow in sanity checking
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0fa81b304a7973a499f844176ca031109487dd31 · < 8d2b1a1ec9f559d30b724877da4ce592edc41fdc| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
CDC-NCM: avoid overflow in sanity checking
A broken device may give an extreme offset like 0xFFF0 and a reasonable length for a fragment. In the sanity check as formulated now, this will create an integer overflow, defeating the sanity check. Both offset and offset + len need to be checked in such a manner that no overflow can occur. And those quantities should be unsigned.
From the CVE record · Linux
The Linux kernel's CDC-NCM fragment sanity check can overflow when a broken device supplies an extreme offset and a reasonable fragment length. The overflow can defeat the sanity check. The input does not establish whether an attacker can control the device or whether authentication or user interaction is required.
Engineers running the Linux kernel should check their versions; affected versions are not specified.