ghsa-989v-m4f5-c899
Vulnerability from github
In the Linux kernel, the following vulnerability has been resolved:
samples/bpf: syscall_tp_user: Fix array out-of-bound access
Commit 06744f24696e ("samples/bpf: Add openat2() enter/exit tracepoint to syscall_tp sample") added two more eBPF programs to support the openat2() syscall. However, it did not increase the size of the array that holds the corresponding bpf_links. This leads to an out-of-bound access on that array in the bpf_object__for_each_program loop and could corrupt other variables on the stack. On our testing QEMU, it corrupts the map1_fds array and causes the sample to fail:
# ./syscall_tp prog #0: map ids 4 5 verify map:4 val: 5 map_lookup failed: Bad file descriptor
Dynamically allocate the array based on the number of programs reported by libbpf to prevent similar inconsistencies in the future
{ affected: [], aliases: [ "CVE-2023-52793", ], database_specific: { cwe_ids: [], github_reviewed: false, github_reviewed_at: null, nvd_published_at: "2024-05-21T16:15:17Z", severity: null, }, details: "In the Linux kernel, the following vulnerability has been resolved:\n\nsamples/bpf: syscall_tp_user: Fix array out-of-bound access\n\nCommit 06744f24696e (\"samples/bpf: Add openat2() enter/exit tracepoint\nto syscall_tp sample\") added two more eBPF programs to support the\nopenat2() syscall. However, it did not increase the size of the array\nthat holds the corresponding bpf_links. This leads to an out-of-bound\naccess on that array in the bpf_object__for_each_program loop and could\ncorrupt other variables on the stack. On our testing QEMU, it corrupts\nthe map1_fds array and causes the sample to fail:\n\n # ./syscall_tp\n prog #0: map ids 4 5\n verify map:4 val: 5\n map_lookup failed: Bad file descriptor\n\nDynamically allocate the array based on the number of programs reported\nby libbpf to prevent similar inconsistencies in the future", id: "GHSA-989v-m4f5-c899", modified: "2024-05-21T18:31:21Z", published: "2024-05-21T18:31:21Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2023-52793", }, { type: "WEB", url: "https://git.kernel.org/stable/c/61576b7a0f28f924da06bead92a39a6d9aa2404a", }, { type: "WEB", url: "https://git.kernel.org/stable/c/9220c3ef6fefbf18f24aeedb1142a642b3de0596", }, { type: "WEB", url: "https://git.kernel.org/stable/c/de4825a444560f8cb78b03dda3ba873fab88bc4f", }, ], schema_version: "1.4.0", severity: [], }
Log in or create an account to share your comment.
This schema specifies the format of a comment related to a security advisory.
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- 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.