CVE-2023-52476
What it is
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)->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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 5.15.137
- Linux Kernel < 6.1.59
- Linux Kernel < 6.5.8
- Linux Kernel 6.6
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-52476.md and follow it. Check whether this project is affected by CVE-2023-52476. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/3863989497652488a50f00e96de4331e5efabc6c
- https://git.kernel.org/stable/c/e53899771a02f798d436655efbd9d4b46c0f9265
- https://git.kernel.org/stable/c/f71edacbd4f99c0e12fe4a4007ab4d687d0688db
- https://git.kernel.org/stable/c/3863989497652488a50f00e96de4331e5efabc6c
- https://git.kernel.org/stable/c/403d201d1fd144cb249836dafb222f6375871c6c
- https://git.kernel.org/stable/c/e53899771a02f798d436655efbd9d4b46c0f9265
- https://git.kernel.org/stable/c/f71edacbd4f99c0e12fe4a4007ab4d687d0688db
References
- https://git.kernel.org/stable/c/3863989497652488a50f00e96de4331e5efabc6c
- https://git.kernel.org/stable/c/e53899771a02f798d436655efbd9d4b46c0f9265
- https://git.kernel.org/stable/c/f71edacbd4f99c0e12fe4a4007ab4d687d0688db
- https://git.kernel.org/stable/c/3863989497652488a50f00e96de4331e5efabc6c
- https://git.kernel.org/stable/c/403d201d1fd144cb249836dafb222f6375871c6c
- https://git.kernel.org/stable/c/e53899771a02f798d436655efbd9d4b46c0f9265
- https://git.kernel.org/stable/c/f71edacbd4f99c0e12fe4a4007ab4d687d0688db