CVE-20XX-?
agent?

CVE-2023-0045

4.7 MEDIUM 2% exploit odds Fix listed

What it is

The current implementation of the prctl syscall does not issue an IBPB immediately during the syscall. The ib_prctl_set  function updates the Thread Information Flags (TIFs) for the task and updates the SPEC_CTRL MSR on the function __speculation_ctrl_update, but the IBPB is only issued on the next schedule, when the TIF bits are checked. This leaves the victim vulnerable to values already injected on the BTB, prior to the prctl syscall.  The patch that added the support for the conditional mitigation via prctl (ib_prctl_set) dates back to the kernel 4.9.176. We recommend upgrading past commit a664ec9158eeddd75121d39c9a0758016097fa96

At a glance

Exploitability
Can be exploited locally on the machine with a low-privilege account. High risk of data exposure.
Exploit odds
2.4% chance of exploitation in the next 30 days (EPSS).
Fix
A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

  1. PublishedDisclosed publicly on CVE.org and NVD
  2. Last updatedMost recent change to the record

Why it ranks here

Details

Published
Last modified
Exploit probability
2.4% · EPSS, next 30 days
Weakness
CWE-610
Record status
Modified

Affected

Attack profile CVSS 3.1 · 4.7

Attack vector
Local
Complexity
High
Privileges needed
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
Raw vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

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-0045.md and follow it. Check whether this project is affected by CVE-2023-0045. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Meme: I wake up, CVE-2023-0045
Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record