CVE-2022-50320

Boot-time kernel oops via invalid FPDT address

Published Sep 15, 2025 · Updated Sep 15, 2025

Improper validation in Linux kernel ACPI FPDT handling allows attackers to trigger a boot-time kernel oops via an invalid physical address. The acpi_init_fpdt path passes an FPDT physical address to acpi_os_map_memory without first verifying that it fits the CPU-supported physical-address range. Reachability requires firmware containing such a malformed FPDT entry; the published failure occurred on a Packard Bell Dot SC with an Intel Atom N2600.

CVSS severity7.8
High
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper validation in Linux kernel ACPI FPDT handling allows attackers to trigger a boot-time kernel oops via an invalid physical address. The acpi_init_fpdt path passes an FPDT physical address to acpi_os_map_memory without first verifying that it fits the CPU-supported physical-address range. Reachability requires firmware containing such a malformed FPDT entry; the published failure occurred on a Packard Bell Dot SC with an Intel Atom N2600.

The record

CVE
CVE-2022-50320
Published
Sep 15, 2025
Updated
Sep 15, 2025
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-787
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 15, 2025CVE publishedPublication date reported by the CVE source.
  2. Sep 15, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <16046a716c8e1f447909bec9b478d58e6e25e513
  2. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <211391bf04b3c74e250c566eeff9cf808156c693
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <30eca146c89d216dda95868ce00a2d35cf73d5a4
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <90bfc9ae875dfbed2e6089516520204cd431dba3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <16046a716c8e1f447909bec9b478d58e6e25e513; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <211391bf04b3c74e250c566eeff9cf808156c693; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <30eca146c89d216dda95868ce00a2d35cf73d5a4; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <90bfc9ae875dfbed2e6089516520204cd431dba3

Published CVSS scores

7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-787Out-of-bounds Write

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo