BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-49357High confidence

efi: Do not import certificates from UEFI Secure Boot for T2 Macs

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-54872

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: efi: Do not import certificates from UEFI Secure Boot for T2 Macs On Apple T2 Macs, when Linux attempts to read the db and dbx efi variables at early boot to load UEFI Secure Boot certificates, a page fault occurs in Apple firmware code and EFI runtime services are disabled with the following logs: [Firmware Bug]: Page fault caused by firmware at PA: 0xffffb1edc0068000 WARNING: CPU: 3 PID: 104 at arch/x86/platform/efi/quirks.c:735 efi_crash_gracefully_on_page_fault+0x50/0xf0 (Removed some logs from here) Call Trace: <TASK> page_fault_oops+0x4f/0x2c0 ? search_bpf_extables+0x6b/0x80 ? search_module_extables+0x50/0x80 ? search_exception_tables+0x5b/0x60 kernelmode_fixup_or_oops+0x9e/0x110 __bad_area_nosemaphore+0x155/0x190 bad_area_nosemaphore+0x16/0x20 do_kern_addr_fault+0x8c/0xa0 exc_page_fault+0xd8/0x180 asm_exc_page_fault+0x1e/0x30 (Removed some logs from here) ? __efi_call+0x28/0x30 ? switch_mm+0x20/0x30 ? efi_call_rts+0x19a/0x8e0 ? process_one_work+0x222/0x3f0 ? worker_thread+0x4a/0x3d0 ? kthread+0x17a/0x1a0 ? process_one_work+0x3f0/0x3f0 ? set_kthread_struct+0x40/0x40 ? ret_from_fork+0x22/0x30 </TASK> ---[ end trace 1f82023595a5927f ]--- efi: Froze efi_rts_wq and disabled EFI Runtime Services integrity: Couldn't get size: 0x8000000000000015 integrity: MODSIGN: Couldn't get UEFI db list efi: EFI Runtime Services are disabled! integrity: Couldn't get size: 0x8000000000000015 integrity: Couldn't get UEFI dbx list integrity: Couldn't get size: 0x8000000000000015 integrity: Couldn't get mokx list integrity: Couldn't get size: 0x80000000 So we avoid reading these UEFI variables and thus prevent the crash.

What

In the Linux kernel, the following vulnerability has been resolved: efi: Do not import certificates from UEFI Secure Boot for T2 Macs On Apple T2 Macs, when Linux attempts to read the db and dbx efi variables at early boot to load UEFI Secure Boot certificates, a page fault occurs in Apple firmware code and EFI runtime services are disabled with the following logs: [Firmware Bug]: Page fault caused by firmware at PA: 0xffffb1edc0068000 WARNING: CPU: 3 PID: 104 at arch/x86/platform/efi/quirks.c:735 efi_crash_gracefully_on_page_fault+0x50/0xf0 (Removed some logs from here) Call Trace: <TASK> page_fault_oops+0x4f/0x2c0 ? search_bpf_extables+0x6b/0x80 ? search_module_extables+0x50/0x80 ? search_exception_tables+0x5b/0x60 kernelmode_fixup_or_oops+0x9e/0x110 __bad_area_nosemaphore+0x155/0x190 bad_area_nosemaphore+0x16/0x20 do_kern_addr_fault+0x8c/0xa0 exc_page_fault+0xd8/0x180 asm_exc_page_fault+0x1e/0x30 (Removed some logs from here) ? __efi_call+0x28/0x30 ? switch_mm+0x20/0x30 ? efi_call_rts+0x19a/0x8e0 ? process_one_work+0x222/0x3f0 ? worker_thread+0x4a/0x3d0 ? kthread+0x17a/0x1a0 ? process_one_work+0x3f0/0x3f0 ? set_kthread_struct+0x40/0x40 ? ret_from_fork+0x22/0x30 </TASK> ---[ end trace 1f82023595a5927f ]--- efi: Froze efi_rts_wq and disabled EFI Runtime Services integrity: Couldn't get size: 0x8000000000000015 integrity: MODSIGN: Couldn't get UEFI db list efi: EFI Runtime Services are disabled! integrity: Couldn't get size: 0x8000000000000015 integrity: Couldn't get UEFI dbx list integrity: Couldn't get size: 0x8000000000000015 integrity: Couldn't get mokx list integrity: Couldn't get size: 0x80000000 So we avoid reading these UEFI variables and thus prevent the crash.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: efi: Do not import certificates from UEFI Secure Boot for T2 Macs On Apple T2 Macs, when Linux attempts to read the db and dbx efi variables at early boot to load UEFI Secure Boot certificates, a page fault occurs in Apple firmware code and EFI runtime services are disabled with the following logs: [Firmware Bug]: Page fault caused by firmware at PA: 0xffffb1edc0068000 WARNING: CPU: 3 PID: 104 at arch/x86/platform/efi/quirks.c:735 efi_crash_gracefully_on_page_fault+0x50/0xf0 (Removed some logs from here) Call Trace: <TASK> page_fault_oops+0x4f/0x2c0 ? search_bpf_extables+0x6b/0x80 ? search_module_extables+0x50/0x80 ? search_exception_tables+0x5b/0x60 kernelmode_fixup_or_oops+0x9e/0x110 __bad_area_nosemaphore+0x155/0x190 bad_area_nosemaphore+0x16/0x20 do_kern_addr_fault+0x8c/0xa0 exc_page_fault+0xd8/0x180 asm_exc_page_fault+0x1e/0x30 (Removed some logs from here) ? __efi_call+0x28/0x30 ? switch_mm+0x20/0x30 ? efi_call_rts+0x19a/0x8e0 ? process_one_work+0x222/0x3f0 ? worker_thread+0x4a/0x3d0 ? kthread+0x17a/0x1a0 ? process_one_work+0x3f0/0x3f0 ? set_kthread_struct+0x40/0x40 ? ret_from_fork+0x22/0x30 </TASK> ---[ end trace 1f82023595a5927f ]--- efi: Froze efi_rts_wq and disabled EFI Runtime Services integrity: Couldn't get size: 0x8000000000000015 integrity: MODSIGN: Couldn't get UEFI db list efi: EFI Runtime Services are disabled! integrity: Couldn't get size: 0x8000000000000015 integrity: Couldn't get UEFI dbx list integrity: Couldn't get size: 0x8000000000000015 integrity: Couldn't get mokx list integrity: Couldn't get size: 0x80000000 So we avoid reading these UEFI variables and thus prevent the crash.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial of service
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2253IBM Security Verify Access: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, sensible Informationen offenzulegen und andere, nicht näher bezeichnete Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250305Security Bulletin 5 March 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 5 March 2025, published on 5 March 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-49339 Référence CVE CVE-2022-49340 https://www.cve.org/CVERecord?id=CVE-2022-49340 Référence CVE CVE-2022-49341 https://www.cve.org/CVERecord?id=CVE-2022-49341 Référence CVE CVE-2022-49343 https://www.cve.org/CVERecord?id=CVE-2022-49343 Référence CVE CVE-2022-49345 https://www.cve.org/CVERecord?id=CVE-2022-49345 Référence CVE CVE-2022-49350 https://www.cve.org/CVERecord?id=CVE-2022-49350 Référence CVE CVE-2022-49352 https://www.cve.org/CVERecord?id=CVE-2022-49352 Référence CVE CVE-2022-49353 https://www.cve.org/CVERecord?id=CVE-2022-49353 Référence CVE CVE-2022-49356 https://www.cve.org/CVERecord?id=CVE-2022-49356 Référence CVE CVE-2022-49357 https://www.cve.org/CVERecord?id=CVE-2022-49357 Référence CVE CVE-2022-49372 https://www.cve.org/CVERecord?id=CVE-2022-49372 Référence CVE CVE-2022-49374 https://www.cve.org/CVERecord?id=CVE-2022-49374 Référence CVE CVE-2022-49376 https://www.cve.org/CVERecord?id=CVE-2022-49376 Référence CVE CVE-2022-49378 https://www.cve.org/CVERecord?id=CVE-2022-49378 Référence CVE CVE-2022-49379 https://www.cve.org/CVERecord?id=CVE-2022-49379 Référence CVE CVE-2022-49384 https://www.cve.org/CVERecord?id=CVE-2022-49384 Référence CVE CVE-2022-49394 https://www.cve.org/CVERecord?id=CVE-2022-49394 Référence CVE CVE-2022-49400 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0336Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49347 Référence CVE CVE-2022-49348 https://www.cve.org/CVERecord?id=CVE-2022-49348 Référence CVE CVE-2022-49349 https://www.cve.org/CVERecord?id=CVE-2022-49349 Référence CVE CVE-2022-49350 https://www.cve.org/CVERecord?id=CVE-2022-49350 Référence CVE CVE-2022-49351 https://www.cve.org/CVERecord?id=CVE-2022-49351 Référence CVE CVE-2022-49352 https://www.cve.org/CVERecord?id=CVE-2022-49352 Référence CVE CVE-2022-49353 https://www.cve.org/CVERecord?id=CVE-2022-49353 Référence CVE CVE-2022-49354 https://www.cve.org/CVERecord?id=CVE-2022-49354 Référence CVE CVE-2022-49356 https://www.cve.org/CVERecord?id=CVE-2022-49356 Référence CVE CVE-2022-49357 https://www.cve.org/CVERecord?id=CVE-2022-49357 Référence CVE CVE-2022-49359 https://www.cve.org/CVERecord?id=CVE-2022-49359 Référence CVE CVE-2022-49362 https://www.cve.org/CVERecord?id=CVE-2022-49362 Référence CVE CVE-2022-49365 https://www.cve.org/CVERecord?id=CVE-2022-49365 Référence CVE CVE-2022-49367 https://www.cve.org/CVERecord?id=CVE-2022-49367 Référence CVE CVE-2022-49368 https://www.cve.org/CVERecord?id=CVE-2022-49368 Référence CVE CVE-2022-49370 https://www.cve.org/CVERecord?id=CVE-2022-49370 Référence CVE CVE-2022-49371 https://www.cve.org/CVERecord?id=CVE-2022-49371 Référence CVE CVE-2022-49372 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0307Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49347 Référence CVE CVE-2022-49348 https://www.cve.org/CVERecord?id=CVE-2022-49348 Référence CVE CVE-2022-49349 https://www.cve.org/CVERecord?id=CVE-2022-49349 Référence CVE CVE-2022-49350 https://www.cve.org/CVERecord?id=CVE-2022-49350 Référence CVE CVE-2022-49351 https://www.cve.org/CVERecord?id=CVE-2022-49351 Référence CVE CVE-2022-49352 https://www.cve.org/CVERecord?id=CVE-2022-49352 Référence CVE CVE-2022-49353 https://www.cve.org/CVERecord?id=CVE-2022-49353 Référence CVE CVE-2022-49354 https://www.cve.org/CVERecord?id=CVE-2022-49354 Référence CVE CVE-2022-49356 https://www.cve.org/CVERecord?id=CVE-2022-49356 Référence CVE CVE-2022-49357 https://www.cve.org/CVERecord?id=CVE-2022-49357 Référence CVE CVE-2022-49359 https://www.cve.org/CVERecord?id=CVE-2022-49359 Référence CVE CVE-2022-49362 https://www.cve.org/CVERecord?id=CVE-2022-49362 Référence CVE CVE-2022-49365 https://www.cve.org/CVERecord?id=CVE-2022-49365 Référence CVE CVE-2022-49367 https://www.cve.org/CVERecord?id=CVE-2022-49367 Référence CVE CVE-2022-49368 https://www.cve.org/CVERecord?id=CVE-2022-49368 Référence CVE CVE-2022-49370 https://www.cve.org/CVERecord?id=CVE-2022-49370 Référence CVE CVE-2022-49371 https://www.cve.org/CVERecord?id=CVE-2022-49371 Référence CVE CVE-2022-49373 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0252Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49346 Référence CVE CVE-2022-49347 https://www.cve.org/CVERecord?id=CVE-2022-49347 Référence CVE CVE-2022-49348 https://www.cve.org/CVERecord?id=CVE-2022-49348 Référence CVE CVE-2022-49349 https://www.cve.org/CVERecord?id=CVE-2022-49349 Référence CVE CVE-2022-49350 https://www.cve.org/CVERecord?id=CVE-2022-49350 Référence CVE CVE-2022-49351 https://www.cve.org/CVERecord?id=CVE-2022-49351 Référence CVE CVE-2022-49352 https://www.cve.org/CVERecord?id=CVE-2022-49352 Référence CVE CVE-2022-49354 https://www.cve.org/CVERecord?id=CVE-2022-49354 Référence CVE CVE-2022-49356 https://www.cve.org/CVERecord?id=CVE-2022-49356 Référence CVE CVE-2022-49357 https://www.cve.org/CVERecord?id=CVE-2022-49357 Référence CVE CVE-2022-49367 https://www.cve.org/CVERecord?id=CVE-2022-49367 Référence CVE CVE-2022-49368 https://www.cve.org/CVERecord?id=CVE-2022-49368 Référence CVE CVE-2022-49370 https://www.cve.org/CVERecord?id=CVE-2022-49370 Référence CVE CVE-2022-49371 https://www.cve.org/CVERecord?id=CVE-2022-49371 Référence CVE CVE-2022-49373 https://www.cve.org/CVERecord?id=CVE-2022-49373 Référence CVE CVE-2022-49375 https://www.cve.org/CVERecord?id=CVE-2022-49375 Référence CVE CVE-2022-49376 https://www.cve.org/CVERecord?id=CVE-2022-49376 Référence CVE CVE-2022-49377 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-026461Linux の Linux Kernel における脆弱性

Linux の Linux Kernel には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Linux: 15ea0e1e3e185040bed6119f815096f2e4326242 < b1cda6dd2c44771f042d65f0d17bec322ef99a0a, 15ea0e1e3e185040bed6119f815096f2e4326242 < c072cab98bac11f6ef9db640fb51834d9552e2e6, 15ea0e1e3e185040bed6119f815096f2e4326242 < 65237307f88f5200782ae7f243bdd385e37cde5d, 15ea0e1e3e185040bed6119f815096f2e4326242 < b34786b25d75f9c119696e6bdf3827f54ae3601b, 15ea0e1e3e185040bed6119f815096f2e4326242 < 1f7264f0510f519b4e4f575a8f0579ea65e7592e, 15ea0e1e3e185040bed6119f815096f2e4326242 < 155ca952c7ca19aa32ecfb7373a32bbc2e1ec6eb, 5.0
Fixed
Linux: < 5.0, 5.4.198 ≤ 5.4.*, 5.10.121 ≤ 5.10.*, 5.15.46 ≤ 5.15.*, 5.17.14 ≤ 5.17.*, 5.18.3 ≤ 5.18.*, 5.19 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 26 Feb 2025 · Last source change 11 May 2026, 18:58 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-54872
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-54872↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-49357 · cve.blacktree.nl