net: bridge: Reject descending VLAN tunnel ranges
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 94339443686b36d3223bc032b7947267474e2679 · < c0444d7499f113d6b7803ef0175591464e17525e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: Reject descending VLAN tunnel ranges
A pair of descending VLAN and tunnel IDs can pass the tunnel range span check. The VLAN subtraction produces a negative int, which is converted to unsigned when compared with the u32 tunnel ID subtraction. It can therefore equal the wrapped tunnel ID delta.
The range loop then performs no iterations. Since the batched notification handling added a post-loop error check, this leaves err uninitialized and makes the request's return value unpredictable.
Reject descending VLAN ranges before comparing the spans. Valid ascending and single-entry ranges remain unchanged, while malformed descending ranges consistently return -EINVAL.
This issue was found by a static analysis checker and confirmed by manual source review.
From the CVE record · Linux
The Linux kernel bridge code can leave an error value uninitialized when processing descending VLAN and tunnel ID ranges, making the request's return value unpredictable. The input does not establish whether an attacker can trigger this, or specify network access, authentication, or user-interaction requirements.
Engineers running the Linux kernel should check their versions; affected versions are not specified.