nvdimm/bus: Fix potential use after free in asynchronous initialization

Affected versions

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

• linux linux kernel4.4.164 and later · before 4.5
• linux linux kernel4.9.137 and later · before 4.10
• linux linux kernel4.14.81 and later · before 4.15
• linux linux kernel4.18.19 and later · before 4.19
• linux linux kernel4.19.2 and later · before 5.10.253
• linux linux kernel5.11 and later · before 5.15.203
• linux linux kernel5.16 and later · before 6.1.167
• linux linux kernel6.2 and later · before 6.6.130
• linux linux kernel6.7 and later · before 6.12.78
• linux linux kernel6.13 and later · before 6.18.20
• linux linux kernel6.19 and later · before 6.19.10
• linux linux kernel7.0

Versions reported by the vendor

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

• Linux Linux

  • 8954771abdea5c34280870e35592c7226a816d95, 3e63a7f25cc85d3d3e174b9b0e3489ebb7eaf4ab, 1490de2bb0836fc0631c04d0559fdf81545b672f, e31a8418c8df7e6771414f99ed3d95ba8aca4e05, 4f1a55a4f990016406147cf3e0c9487bf83e50f0, 4.20affected
  • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before 6fc36c2a925ceaba203eb13d75a8f0879a2c121baffected · git
  • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before a36cf138500e56f50db9f9a33222df6969b38326affected · git
  • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before 9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4daffected · git
  • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20eaffected · git
  • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before 2c638259ad750833fd46a0cf57672a618542d84caffected · git
  • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before a226e5b49e5fe8c98b14f8507de670189d191348affected · git
  • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before 84af19855d1abdee3c9d57c0684e2868e391793caffected · git
  • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before a8aec14230322ed8f1e8042b6d656c1631d41163affected · git
  • 4.4.164 and later · before 4.5affected · semver

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
• CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV
  77This week
• CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV
  77This week
• CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV
  77This week

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.