ipack: ipoctal: fix stack information leak
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ba4dc61fe8c545a5d6a68b63616776556b771f51 · < 5f6a309a699675680df15d9b6d389114515b4426| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ipack: ipoctal: fix stack information leak
The tty driver name is used also after registering the driver and must specifically not be allocated on the stack to avoid leaking information to user space (or triggering an oops).
Drivers should not try to encode topology information in the tty device name but this one snuck in through staging without anyone noticing and another driver has since copied this malpractice.
Fixing the ABI is a separate issue, but this at least plugs the security hole.
From the CVE record · Linux
The ipack ipoctal tty driver uses a stack-allocated driver name after registration. A user-space attacker with access to the affected tty may obtain stack information or trigger a kernel oops; the input does not specify authentication requirements.
Engineers running Linux kernels with the ipack ipoctal driver should check their installations; affected versions are not specified.