CVE-2023-4134: Kernel: cyttsp4_core: use-after-free in cyttsp4_watchdog_work()

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• fedoraproject fedora38
• linux linux kernelbefore 6.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (fedora). Independent of NVD's CPE analysis and usually ahead of it.

• github.com/torvalds/linux kernel

  • dbe836576f12743a7d2d170ad4ad4fd324c4d47a and laternot affected · git

• Red Hat Red Hat Enterprise Linux 6

  • all versionsunknown

• Red Hat Red Hat Enterprise Linux 7

  • all versionsunknown
  • all versionsunknown

• Red Hat Red Hat Enterprise Linux 8

  • all versionsunknown
  • all versionsunknown

• Red Hat Red Hat Enterprise Linux 9

  • all versionsunknown
  • all versionsunknown

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
  89Now
• CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
  85Now
• CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
  83Now

Published before and after this one in the same product

• ← EarlierCVE-2024-50262Nov 9, 2024 · bpf: Fix out-of-bounds write in trie_get_next_key()
  31Monitor
• ← EarlierCVE-2024-50263Nov 11, 2024 · fork: only invoke khugepaged, ksm hooks if no error
  22Monitor
• Later →CVE-2023-4458Nov 14, 2024 · Kernel: ksmbd: smb2_open out-of-bounds read information disclosure vulnerability
  30Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1free(dev->buf);2/* ... another thread is still running ... */3process(dev->buf);

1lock(&dev->lock);2free(dev->buf);3dev->buf = NULL;4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.