CVE-2023-53474

x86/MCE/AMD: Use an u64 for bank_map

MEDIUM
5.5
CVSS Score
Published: October 1, 2025 at 11:42 AM UTC
Updated: October 15, 2026 at 10:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: x86/MCE/AMD: Use an u64 for bank_map Thee maximum number of MCA banks is 64 (MAX_NR_BANKS), see a0bc32b3cacf ("x86/mce: Increase maximum number of banks to 64"). However, the bank_map which contains a bitfield of which banks to initialize is of type unsigned int and that overflows when those bit numbers are >= 32, leading to UBSAN complaining correctly: UBSAN: shift-out-of-bounds in arch/x86/kernel/cpu/mce/amd.c:1365:38 shift exponent 32 is too large for 32-bit type 'int' Change the bank_map to a u64 and use the proper BIT_ULL() macro when modifying bits in there. [ bp: Rewrite commit message. ]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10 ≤ v < 5.10.1805.11 ≤ v < 5.15.1115.16 ≤ v < 6.1.286.2 ≤ v < 6.2.156.3 ≤ v < 6.3.25.10a0bc32b3cacf194dc479b342f006203fd1e1941a
Vendor states this is fixed in 11c58a0c1937c157dbdf82d5ab634d68c99f3098 (fixed)
Vendor states this is fixed in 4c1cdec319b9aadb65737c3eb1f5cb74bd6aa156 (fixed)
Vendor states this is fixed in 67bb7521b6420d81dab7538c0686f18f7d6d09f4 (fixed)
Vendor states this is fixed in 9669fa17287c3af2bbd4868d4c8fdd9e57f8332e (fixed)
Vendor states this is fixed in a9b9ea0e63a0ec5e97bf1219ab6dcbd55e362f83 (fixed)
Vendor states this is fixed in ba8ffb1251eb629c2ec35220e3896cf4f7b888a7 (fixed)
Vendor states this is fixed in 5.10 (unaffected)
Vendor states this is fixed in 5.10.180 (unaffected)
Vendor states this is fixed in 5.15.111 (unaffected)
Vendor states this is fixed in 6.1.28 (unaffected)
Vendor states this is fixed in 6.2.15 (unaffected)
Vendor states this is fixed in 6.3.2 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-190

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card