Skip to content
Fencer Vulns
high 7.8

CVE-2023-53474 json

x86/MCE/AMD: Use an u64 for bank_map

published 2025-10-01 13 mo ago modified 2026-10-15 24 d ago also EUVD-2025-32810

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits
0
none known

Summary

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. ]

Patch / fix

  • Linux Linux 5.10.180, 5.15.111, 6.1.28, 6.2.15, 6.3.2, 6.4
  • linux Debian 12 6.1.37-1
  • linux Debian 14, Debian 13 6.3.7-1

debian advisories DEBIAN-CVE-2023-53474

  • linux Ubuntu 22.04 LTS 5.15.0-79.86
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1042.47
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1039.47
  • linux-gke Ubuntu 22.04 LTS 5.15.0-1039.44
  • linux-ibm Ubuntu 22.04 LTS 5.15.0-1035.38
  • linux-kvm Ubuntu 22.04 LTS 5.15.0-1039.44
  • linux-azure Ubuntu 22.04 LTS 5.15.0-1045.52
  • linux-gkeop Ubuntu 22.04 LTS 5.15.0-1025.30

ubuntu advisories UBUNTU-CVE-2023-53474

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-rt SLE Micro 5.5 5.14.21-150500.13.109.1
  • kernel-source-rt SLE Micro 5.5 5.14.21-150500.13.109.1
  • kernel-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.133.1
  • kernel-source-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.133.1
  • kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.179.1
  • kernel-syms SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +3 more 5.14.21-150400.24.179.1
  • kernel-source SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +3 more 5.14.21-150400.24.179.1
  • kernel-default SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +7 more 5.14.21-150400.24.179.1

suse advisories SUSE-SU-2025:3761-1SUSE-SU-2025:3716-1SUSE-SU-2025:03628-1SUSE-SU-2025:03615-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-53474 updated cvss 1.9

kernel: x86/MCE/AMD: Use an u64 for bank_map

  • Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 10 kernel
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
24 d ago

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.