UBUNTU-CVE-2025-22104: Buffer Overflow
In the Linux kernel, the following vulnerability has been resolved: ibmvnic: Use kernel helpers for hex dumps Previously, when the driver was printing hex dumps, the buffer was cast to an 8 byte long and printed using string formatters. If the buffer size was not a multiple of 8 then a read buffer overflow was possible. Therefore, create a new ibmvnic function that loops over a buffer and calls hexdumptobuffer instead. This patch address KASAN reports like the one below: ibmvnic 30000003 env3: Login Buffer: ibmvnic 30000003 env3: 01000000af000000 <...> ibmvnic 30000003 env3: 2e6d62692e736261 ibmvnic 30000003 env3: 65050003006d6f63 ================================================================== BUG: KASAN: slab-out-of-bounds in ibmvniclogin+0xacc/0xffc [ibmvnic] Read of size 8 at addr c0000001331a9aa8 by task ip/17681 <...> Allocated by task 17681: <...> ibmvniclogin+0x2f0/0xffc [ibmvnic] ibmvnicopen+0x148/0x308 [ibmvnic] devopen+0x1ac/0x304 <...> The buggy address is located 168 bytes inside of allocated 175-byte region [c0000001331a9a00, c0000001331a9aaf) <...> ================================================================= ibmvnic 30000003 env3: 000000000033766e
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-nvidia-tegrato a version that resolves this vulnerability.Fixed in 6.8.0-1035.38
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems running one of the listed Ubuntu kernel packages are potentially exposed when the ibmvnic driver is in use. The issue occurs in the driver's logging of login-buffer hex dumps.
What does an attacker need to exploit the vulnerability?
The supplied severity vector indicates local access and low privileges are required, with no user interaction. The description does not identify a remote attack path or additional prerequisite beyond reaching the affected driver behavior.
What is the impact if exploitation succeeds?
The vulnerability is a slab out-of-bounds read caused by processing a buffer whose length is not a multiple of eight. The provided vector rates confidentiality and availability impact as high, while integrity impact is listed as none.
How can I identify evidence of the issue?
KASAN-enabled systems may report a "slab-out-of-bounds" read in ibmvnic_login, including a read of size 8 and ibmvnic stack frames. The logs may also show ibmvnic Login Buffer hex-dump output near the report.
What is the mitigation when an update cannot be applied immediately?
The provided data does not specify a workaround. Reducing use of the affected ibmvnic driver where operationally possible would avoid the vulnerable logging path, but the described resolution is to use kernel helpers for hex dumps.