cve-2022-49889
Vulnerability from cvelistv5
Published
2025-05-01 14:10
Modified
2025-05-01 14:10
Severity ?
EPSS score ?
Summary
ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters()
References
{ "containers": { "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "Linux", "programFiles": [ "kernel/trace/ring_buffer.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "lessThan": "b5074df412bf3df9d6ce096b6fa03eb1082d05c9", "status": "affected", "version": "2475de2bc0de17fb1b24c5e90194f84b5ca70d3e", "versionType": "git" }, { "lessThan": "49ca992f6e50d0f46ec9608f44e011cf3121f389", "status": "affected", "version": "f4f15344110d0b5b8822ac97bc8200e71939c945", "versionType": "git" }, { "lessThan": "7433632c9ff68a991bd0bc38cabf354e9d2de410", "status": "affected", "version": "f3ddb74ad0790030c9592229fb14d8c451f4e9a8", "versionType": "git" } ] }, { "defaultStatus": "unaffected", "product": "Linux", "programFiles": [ "kernel/trace/ring_buffer.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "lessThan": "5.15.78", "status": "affected", "version": "5.15.75", "versionType": "semver" }, { "lessThan": "6.0.8", "status": "affected", "version": "6.0.3", "versionType": "semver" } ] } ], "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters()\n\nOn some machines the number of listed CPUs may be bigger than the actual\nCPUs that exist. The tracing subsystem allocates a per_cpu directory with\naccess to the per CPU ring buffer via a cpuX file. But to save space, the\nring buffer will only allocate buffers for online CPUs, even though the\nCPU array will be as big as the nr_cpu_ids.\n\nWith the addition of waking waiters on the ring buffer when closing the\nfile, the ring_buffer_wake_waiters() now needs to make sure that the\nbuffer is allocated (with the irq_work allocated with it) before trying to\nwake waiters, as it will cause a NULL pointer dereference.\n\nWhile debugging this, I added a NULL check for the buffer itself (which is\nOK to do), and also NULL pointer checks against buffer-\u003ebuffers (which is\nnot fine, and will WARN) as well as making sure the CPU number passed in\nis within the nr_cpu_ids (which is also not fine if it isn\u0027t).\n\n\nBugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1204705" } ], "providerMetadata": { "dateUpdated": "2025-05-01T14:10:33.832Z", "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux" }, "references": [ { "url": "https://git.kernel.org/stable/c/b5074df412bf3df9d6ce096b6fa03eb1082d05c9" }, { "url": "https://git.kernel.org/stable/c/49ca992f6e50d0f46ec9608f44e011cf3121f389" }, { "url": "https://git.kernel.org/stable/c/7433632c9ff68a991bd0bc38cabf354e9d2de410" } ], "title": "ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters()", "x_generator": { "engine": "bippy-1.1.0" } } }, "cveMetadata": { "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "assignerShortName": "Linux", "cveId": "CVE-2022-49889", "datePublished": "2025-05-01T14:10:33.832Z", "dateReserved": "2025-05-01T14:05:17.242Z", "dateUpdated": "2025-05-01T14:10:33.832Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2022-49889\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-05-01T15:16:13.897\",\"lastModified\":\"2025-05-01T15:16:13.897\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters()\\n\\nOn some machines the number of listed CPUs may be bigger than the actual\\nCPUs that exist. The tracing subsystem allocates a per_cpu directory with\\naccess to the per CPU ring buffer via a cpuX file. But to save space, the\\nring buffer will only allocate buffers for online CPUs, even though the\\nCPU array will be as big as the nr_cpu_ids.\\n\\nWith the addition of waking waiters on the ring buffer when closing the\\nfile, the ring_buffer_wake_waiters() now needs to make sure that the\\nbuffer is allocated (with the irq_work allocated with it) before trying to\\nwake waiters, as it will cause a NULL pointer dereference.\\n\\nWhile debugging this, I added a NULL check for the buffer itself (which is\\nOK to do), and also NULL pointer checks against buffer-\u003ebuffers (which is\\nnot fine, and will WARN) as well as making sure the CPU number passed in\\nis within the nr_cpu_ids (which is also not fine if it isn\u0027t).\\n\\n\\nBugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1204705\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/49ca992f6e50d0f46ec9608f44e011cf3121f389\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/7433632c9ff68a991bd0bc38cabf354e9d2de410\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/b5074df412bf3df9d6ce096b6fa03eb1082d05c9\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}" } }
Loading...
Loading...
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.