LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50159: of: check previous kernel's ima-kexec-buffer against memory bounds

In the Linux kernel, the following vulnerability has been resolved: of: check previous kernel's ima-kexec-buffer against memory bounds Presently ima_get_kexec_buffer() doesn't check if the previous kernel's ima-kexec-buffer lies outside the addressable memory range. This can result in a kernel panic if the new kernel is booted with 'mem=X' arg and the ima-kexec-buffer was allocated beyond that range by the previous kernel. The panic is usually of the form below: $ sudo kexec --initrd initrd vmlinux --append='mem=16G' <snip> BUG: Unable to handle kernel data access on read at 0xc000c01fff7f0000 Faulting instruction address: 0xc000000000837974 Oops: Kernel access of bad area, sig: 11 [#1] <snip> NIP [c000000000837974] ima_restore_measurement_list+0x94/0x6c0 LR [c00000000083b55c] ima_load_kexec_buffer+0xac/0x160 Call Trace: [c00000000371fa80] [c00000000083b55c] ima_load_kexec_buffer+0xac/0x160 [c00000000371fb00] [c0000000020512c4] ima_init+0x80/0x108 [c00000000371fb70] [c0000000020514dc] init_ima+0x4c/0x120 [c00000000371fbf0] [c000000000012240] do_one_initcall+0x60/0x2c0 [c00000000371fcc0] [c000000002004ad0] kernel_init_freeable+0x344/0x3ec [c00000000371fda0] [c0000000000128a4] kernel_init+0x34/0x1b0 [c00000000371fe10] [c00000000000ce64] ret_from_kernel_thread+0x5c/0x64 Instruction dump: f92100b8 f92100c0 90e10090 910100a0 4182050c 282a0017 3bc00000 40810330 7c0802a6 fb610198 7c9b2378 f80101d0 <a1240000> 2c090001 40820614 e9240010 ---[ end trace 0000000000000000 ]--- Fix this issue by checking returned PFN range of previous kernel's ima-kexec-buffer with page_is_ram() to ensure correct memory bounds.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash a newly booted kernel during a kexec transition when IMA state from the previous kernel sits outside the new kernel's usable memory range. The known impact is availability disruption, not confirmed data theft or privilege escalation.

Executive priority

Treat as a targeted availability risk, not a broad emergency. Prioritize remediation where kexec and IMA are used in production or recovery workflows.

Technical view

ima_get_kexec_buffer() failed to validate whether the previous kernel's ima-kexec-buffer was within addressable RAM. With constrained memory on the new boot, IMA restore could read invalid memory and panic. The fix validates the returned PFN range with page_is_ram().

Likely exposure

Exposure appears limited to Linux systems using kexec with IMA measurement handoff, especially where boot memory is constrained. The source lists Linux kernel versions as affected but provides no distribution package mapping.

Exploitation context

No KEV listing and no cited source reports active exploitation. The public description shows a crash condition during a specific kexec boot scenario, but does not establish remote exploitability or attacker prerequisites.

Researcher notes

Evidence supports a kernel panic caused by missing bounds validation in the IMA kexec buffer path. CVSS, CWE, attacker requirements, and distribution-specific affected package ranges are not provided in the source bundle.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Check Linux distribution advisories for package-specific fixed versions.
  • Prioritize systems using kexec, IMA, or constrained boot memory settings.
  • Avoid operational boot configurations that trigger this condition until patched.

Validation and detection

  • Inventory Linux kernels and compare against vendor fixed package versions.
  • Identify hosts using kexec and IMA measurement list preservation.
  • Review boot configurations for constrained memory arguments.
  • Confirm updated kernels include the stable memory-bounds validation fix.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50159 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux467d27824920e866af148132f555d40ca1fb199e, 467d27824920e866af148132f555d40ca1fb199e, 467d27824920e866af148132f555d40ca1fb199e, 467d27824920e866af148132f555d40ca1fb199eunaffected
LinuxLinux4.10, 0, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.