arm64: asm-bug: Add .align 2 to the end of __BUG_ENTRY
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9fb7410f955f7a62c1f882ca8f9ffd4525907e28 · < 9f2ad88f9b349554f64e4037ec185c84d7dd9c7d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
arm64: asm-bug: Add .align 2 to the end of __BUG_ENTRY
When CONFIG_DEBUG_BUGVERBOSE=n, we fail to add necessary padding bytes to bug_table entries, and as a result the last entry in a bug table will be ignored, potentially leading to an unexpected panic(). All prior entries in the table will be handled correctly.
The arm64 ABI requires that struct fields of up to 8 bytes are naturally-aligned, with padding added within a struct such that struct are suitably aligned within arrays.
When CONFIG_DEBUG_BUGVERPOSE=y, the layout of a bug_entry is:
struct bug_entry { signed int bug_addr_disp; // 4 bytes signed int file_disp; // 4 bytes unsigned short line; // 2 bytes unsigned short flags; // 2 bytes }
... with 12 bytes total, requiring 4-byte alignment.
When CONFIG_DEBUG_BUGVERBOSE=n, the layout of a bug_entry is:
From the CVE record · Linux
On arm64 Linux kernels built with CONFIG_DEBUG_BUGVERBOSE=n, the final bug-table entry in a module can lack required padding and be skipped. Loading a module that triggers that entry can cause an unexpected kernel panic. The input does not establish a network attack path or specific authentication requirements.
Engineers running arm64 Linux kernels with CONFIG_DEBUG_BUGVERBOSE=n should check their kernel versions against the vendor advisory; affected versions are not specified in the input.