LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48967: NFC: nci: Bounds check struct nfc_target arrays

In the Linux kernel, the following vulnerability has been resolved: NFC: nci: Bounds check struct nfc_target arrays While running under CONFIG_FORTIFY_SOURCE=y, syzkaller reported: memcpy: detected field-spanning write (size 129) of single field "target->sensf_res" at net/nfc/nci/ntf.c:260 (size 18) This appears to be a legitimate lack of bounds checking in nci_add_new_protocol(). Add the missing checks.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-48967 is a Linux kernel NFC issue where malformed NFC target data could write past a fixed-size field. The public record does not provide CVSS severity, a CWE, or confirmed exploitation. Business urgency depends on whether affected Linux systems actually use NFC/NCI functionality.

Executive priority

Set this as a targeted Linux patch-management item, not a broad emergency, unless your environment relies on NFC-enabled Linux endpoints or embedded devices. The absence of CVSS, KEV, and exploitation evidence lowers confidence in urgency, but memory-safety bugs in kernel code still warrant timely remediation.

Technical view

The flaw is missing bounds checks in Linux kernel NFC NCI nci_add_new_protocol(). With CONFIG_FORTIFY_SOURCE=y, syzkaller detected a field-spanning memcpy write to target->sensf_res, whose field size was smaller than the copied data. Kernel stable commits add bounds checks.

Likely exposure

Exposure is most plausible on Linux systems running affected kernels with NFC/NCI support enabled and relevant NFC hardware or drivers present. General server fleets without NFC capability likely have limited exposure, but this should be confirmed from kernel configuration and asset inventory.

Exploitation context

The supplied sources show syzkaller discovery and kernel fixes. They do not show active exploitation, public exploit use, KEV listing, attack prerequisites, or impact beyond the bounds-check failure. Treat exploitability as not established from the provided evidence.

Researcher notes

Key evidence is the kernel description: CONFIG_FORTIFY_SOURCE detected a memcpy field-spanning write, and the fix adds missing bounds checks in nci_add_new_protocol(). The affected-version data is sparse and branch-specific; rely on distribution advisories and the listed stable commits for validation.

Mitigation direction

  • Identify Linux kernels matching the affected version data in the CVE record.
  • Apply vendor or kernel stable updates containing the referenced NFC NCI bounds-check fixes.
  • Where NFC is unnecessary, consider disabling NFC support through approved platform controls.
  • Monitor distribution advisories for backported fixes and package-specific affected ranges.
  • Prioritize embedded, mobile, kiosk, and endpoint systems more likely to expose NFC.

Validation and detection

  • Check kernel version and distribution advisory status for each Linux asset.
  • Confirm whether NFC/NCI kernel support is built, loaded, or available.
  • Verify installed kernel includes the relevant stable fix for its branch.
  • Review asset inventory for systems with NFC hardware or NFC-dependent workflows.
  • Document exceptions where vendor guidance is unavailable or exposure cannot be confirmed.
Prepared
Confidence
medium
Sources
10

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-48967 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
1ADP providers
9Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5, 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5, 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5, 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5, 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5, 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5, 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5, 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5unaffected
LinuxLinux3.4, 0, 4.9.336, 4.14.302, 4.19.269, 5.4.227, 5.10.159, 5.15.83, 6.0.13, 6.1affected
Weakness

CWE details

No CWE listed

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