CVE-2023-52476 Affecting kernel-rt-debuginfo-common-x86_64 package, versions <0:4.18.0-553.22.1.rt7.363.el8_10


Severity

Recommended
high

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
0.05% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ROCKY8-KERNELRTDEBUGINFOCOMMONX8664-8134348
  • published1 Oct 2024
  • disclosed29 Feb 2024

Introduced: 29 Feb 2024

CVE-2023-52476  (opens in a new tab)

How to fix?

Upgrade Rocky-Linux:8 kernel-rt-debuginfo-common-x86_64 to version 0:4.18.0-553.22.1.rt7.363.el8_10 or higher.
This issue was patched in RLSA-2024:7001.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-rt-debuginfo-common-x86_64 package and not the kernel-rt-debuginfo-common-x86_64 package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux:8 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

perf/x86/lbr: Filter vsyscall addresses

We found that a panic can occur when a vsyscall is made while LBR sampling is active. If the vsyscall is interrupted (NMI) for perf sampling, this call sequence can occur (most recent at top):

__insn_get_emulate_prefix()
insn_get_emulate_prefix()
insn_get_prefixes()
insn_get_opcode()
decode_branch_type()
get_branch_type()
intel_pmu_lbr_filter()
intel_pmu_handle_irq()
perf_event_nmi_handler()

Within __insn_get_emulate_prefix() at frame 0, a macro is called:

peek_nbyte_next(insn_byte_t, insn, i)

Within this macro, this dereference occurs:

(insn)-&gt;next_byte

Inspecting registers at this point, the value of the next_byte field is the address of the vsyscall made, for example the location of the vsyscall version of gettimeofday() at 0xffffffffff600000. The access to an address in the vsyscall region will trigger an oops due to an unhandled page fault.

To fix the bug, filtering for vsyscalls can be done when determining the branch type. This patch will return a "none" branch if a kernel address if found to lie in the vsyscall region.

CVSS Scores

version 3.1