Sign inStart freeBook a demo

What is CVE-2022-40261?A high-severity flaw in Nuc M15 Laptop Kit Lapbc510 Firmware, explained.

High severity5 affected products
The short answer

CVE-2022-40261 is a high-severity flaw (CVSS 8.2) in Nuc M15 Laptop Kit Lapbc510 Firmware from Intel, published on 20 September 2022. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.4%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 20 September 2022. Record last updated 28 May 2025. We keep this page's data up to date.

What it does

What is CVE-2022-40261? In plain terms.

An attacker has to be already on the device with an administrator account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

The official description

An attacker can exploit this vulnerability to elevate privileges from ring 0 to ring -2, execute arbitrary code in System Management Mode - an environment more privileged than operating system (OS) and completely isolated from it. Running arbitrary code in SMM additionally bypasses SMM-based SPI flash protections against modifications, which can help an attacker to install a firmware backdoor/implant into BIOS. Such a malicious firmware code in BIOS could persist across operating system re-installs. Additionally, this vulnerability potentially could be used by malicious actors to bypass security mechanisms provided by UEFI firmware (for example, Secure Boot and some types of memory isolation for hypervisors). This issue affects: Module name: OverClockSmiHandler SHA256: a204699576e1a48ce915d9d9423380c8e4c197003baf9d17e6504f0265f3039c Module GUID: 4698C2BD-A903-410E-AD1F-5EEF3A1AE422

What kind of flaw is it?

  • CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
CVSS 3.1 scoreHigh · 8.2

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAlready on the device
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstAn administrator account
  • Does someone have to clickNo, nobody has to do anything
  • What an attacker getsCan read data, change data and take it offline

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

Exploitation

Is CVE-2022-40261 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.4%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days0.4%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
How Precursor Intelligence ranks it
51out of 100Medium

CVE-2022-40261 scores 51. Action: Plan remediation.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2022-40261 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2022-40261? 5 products.

The published record lists 5 products from 2 vendors. If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2022-40261? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

2 links
Precursor Intelligence

Does CVE-2022-40261 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2022-40261 is a high-severity flaw in Nuc M15 Laptop Kit Lapbc510 Firmware from Intel, published on 20 September 2022. An attacker has to be already on the device with an administrator account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

It scores 8.2 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2022-40261 is 51 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.4%. That can change at any time, which is why we keep watching.

For Nuc M15 Laptop Kit Lapbc510 Firmware from Intel: version not specified. The record lists 5 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring