Local privilege escalation in udev via malicious hardware devices
Key facts
- Attack vector
- Physical
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-vpfq-8p5f-jcqx. Fix status from GitHub.
Summary
udev versions before 260 are affected. The scsi_id and v4l_id helper programs pass device properties from the kernel to userspace without sanitizing them, so a crafted property can inject extra udev rules. An attacker with physical access who plugs in a malicious USB or SCSI device can make udev run an executable of the attacker's choice as root.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Impact udev's `scsi_id` and `v4l_id` helper binaries, which parse input from the kernel, are vulnerable to malicious devices being plugged in, with intentionally crafted properties exposed to the respective kernel drivers, that send them down to userspace without sanitization. For `v4l_id`, the `ID_V4L_PRODUCT` property is derived from the USB descriptor, and a custom device can set it to `foo\nREMOVE_CMD=/path/to/exe` to have udev run the selected executable as root. For `scsi_id`, the `ID_SCSI_SERIAL` property is derived from the hardware's SCSI serial, which can be crafted to contain `\n SYSTEMD_WANTS=foobar.service` so that it can be used to activate a unit of the attacker's choice, including `debug-shell.service` which spawns a root console. ### Patches v260 https://github.com/systemd/systemd/commit/16325b35fa6ecb25f66534a562583ce3b96d52f3 https://github.com/systemd/systemd/commit/54f880b02ecf7362e630ffc885d1466df6ee6820 v259.5 https://github.com/systemd/systemd/commit/3513862eabe9ec4a6a095d7266e98f998f289ed2 https://github.com/systemd/systemd/commit/4425d8523e79f3cc00b3b93a0b5e7c6cdc284a97 v258.7 https://github.com/systemd/systemd/commit/c20d21e0da293e715db468f9f4a15a5c8fbf8273 https://github.com/systemd/systemd/commit/75c585beae60e73208941e6b3f64cf249223f53d v257.13 https://github.com/systemd/systemd/commit/03bb697b8df0339c37f4b845025320b261aeb7cc https://github.com/systemd/systemd/commit/5887e72ff87d3a66a4c3fa91897fbec1545f4d3d ### Workarounds Disable the v4l and iscsi drivers in the kernel ### References Originally reported on yeswehack.com as YWH-PGM9780-98 and YWH-PGM9780-99
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | udev (linux) | < 260 | 260 259.5 258.7 257.13 | Patch available | GHSA-vpfq-8p5f-jcqx |
- udev (linux) Vendor— Affected < 260 Fixed in 260 259.5 258.7 257.13 Patch available GHSA-vpfq-8p5f-jcqx
Remediation
Upgrade udev to version 260, 259.5, 258.7 or 257.13, matching the release branch in use. The sources give a workaround of disabling the v4l and iscsi drivers in the kernel.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-vpfq-8p5f-jcqx udev (linux) Fixed in 260 259.5 258.7 257.13 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-vpfq-8p5f-jcqx
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences