mlxbf-bootctl: use sysfs_emit_at() in secure_boot_fuse_state_show()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mlxbf-bootctl: use sysfs_emit_at() in secure_boot_fuse_state_show()
A warning is seen when running the latest kernel on a BlueField SOC: [251.512704] ------------[ cut here ]------------ [251.512711] invalid sysfs_emit: buf:0000000003aa32ae [251.512720] WARNING: CPU: 1 PID: 705264 at fs/sysfs/file.c:767 sysfs_emit+0xac/0xc8
The warning is triggered because the mlxbf-bootctl driver invokes "sysfs_emit()" with a buffer pointer that is not aligned to the start of the page. The driver should instead use "sysfs_emit_at()" to support non-zero offsets into the destination buffer.
From the CVE record · Linux
On BlueField SoCs, the Linux kernel's mlxbf-bootctl driver can trigger a sysfs warning because it passes a buffer pointer with a non-zero offset to sysfs_emit(). The input does not describe an attacker action or specify network access, authentication, or user-interaction requirements.
Engineers running the Linux kernel on BlueField SoCs should check their systems; affected versions are not specified.