perf/core: Fix a refcount leak in attach_perf_ctx_data()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.55, 7.2.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: perf/core: Fix a refcount leak in attach_perf_ctx_data() The attach_perf_ctx_data() can race on global and !global cases. The global case is protected by global_ctx_data_rwsem and shares a single reference count using perf_ctx_data.global field. But when it races with !global case, it may miss to set the global field and result in a reference count leak. CPU1 CPU2 ---------------------------------------------------------------- attach_task_ctx_data(.global=1) attach_task_ctx_data(.global=0) cd1 = alloc_perf_ctx_data(); cd2 = alloc_perf_ctx_data(); // { .global = 0, .refcount = 1 }; try_cmpxchg(); // success, // task->perf_ctx_data = cd2 try_cmpxhg(); // fail; old = cd2 refcount_inc_not_zero(&old->refcount); // success // old.refcount = 2 free_perf_ctx_data(cd1); Then later detach_global_ctx_data() will see the data but it's not marked as global, so it won't call detach_task_ctx_data().
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 506e64e710ff9573fd2b86686528762b7901b5e4 · fixed in 23250517cd475367653f1e99396967f54c6f1b7c; From 506e64e710ff9573fd2b86686528762b7901b5e4 · fixed in 5286d4eb5cd7e10d7d93c3cc596e18bc8ad80f72; From 506e64e710ff9573fd2b86686528762b7901b5e4 · fixed in cca4980630b3c7a85f53cb43c6018184ce5d4e37
- Linux Linux
6.15
- KernelLinux
From 6.15.0 · fixed in 6.18.55; From 6.19.0 · fixed in 7.2.9