LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48832: audit: don't deref the syscall args when checking the openat2 open_how::flags

In the Linux kernel, the following vulnerability has been resolved: audit: don't deref the syscall args when checking the openat2 open_how::flags As reported by Jeff, dereferencing the openat2 syscall argument in audit_match_perm() to obtain the open_how::flags can result in an oops/page-fault. This patch fixes this by using the open_how struct that we store in the audit_context with audit_openat2_how(). Independent of this patch, Richard Guy Briggs posted a similar patch to the audit mailing list roughly 40 minutes after this patch was posted.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel audit bug where handling an openat2 system call could trigger a kernel oops or page fault. The public record does not provide CVSS, CWE, exploit evidence, or broad product mapping. Treat it as a stability and availability risk until your kernel vendor confirms exposure.

Executive priority

Handle through normal kernel patch governance unless your environment has affected 5.16-era kernels or unexplained kernel oops events. There is insufficient public evidence for emergency response based on this bundle alone.

Technical view

audit_match_perm() dereferenced an openat2 syscall argument to read open_how::flags. The fix changes audit code to use the open_how value already stored in audit_context by audit_openat2_how(), avoiding the unsafe dereference that could fault.

Likely exposure

Exposure is limited to Linux systems in the affected kernel range identified by the CVE record, especially 5.16-era kernels. Distribution kernels may differ because vendors often backport fixes, so version strings alone are not conclusive.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked KEV. The record describes a kernel oops/page-fault condition, but does not provide exploitability detail, attacker prerequisites, or observed abuse.

Researcher notes

The source bundle names the vulnerable logic and the fix approach, but omits CVSS, CWE, CPEs, prerequisites, and exploit analysis. Research should focus on affected kernel provenance, audit subsystem configuration, and vendor backport status.

Mitigation direction

  • Check your Linux vendor advisory for CVE-2022-48832 coverage.
  • Update affected kernels to a vendor-supported build containing the cited audit fix.
  • Prioritize internet-facing or multi-user Linux hosts after vendor confirmation.
  • Track distribution backports instead of relying only on upstream version numbers.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Confirm whether the cited stable commits or vendor backports are present.
  • Review kernel logs for audit/openat2-related oops or page-fault events.
  • Validate remediation through vendor package metadata or kernel changelogs.
Prepared
Confidence
medium
Sources
4

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-48832 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
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1c30e3af8a79260cdba833a719209b01e6b92300, 1c30e3af8a79260cdba833a719209b01e6b92300unaffected
LinuxLinux5.16, 0, 5.16.10, 5.17affected
Weakness

CWE details

No CWE listed

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