ASoC: meson: Keep link pointers valid on realloc failure
- 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 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- 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: ASoC: meson: Keep link pointers valid on realloc failure meson_card_reallocate_links() grows the DAI link and private data arrays with two consecutive krealloc() calls and updates the owner pointers only after both calls have succeeded. A successful krealloc() may move the data: it frees the old block and returns a new one. When that happens for the link array and the second krealloc() then fails, card->dai_link still points to the block that krealloc() already freed, and the error path frees the new block too. The probe error path then calls meson_card_clean_references(), which dereferences card->dai_link and kfree()s it again, resulting in a use-after-free and a double free. Commit card->dai_link and card->num_links right after the first krealloc() succeeds, so the pointer always refers to a valid allocation that meson_card_clean_references() can walk and free. krealloc() with __GFP_ZERO zero-initializes the added entries, so walking them on the error path is safe. With both failure paths reduced to a plain return, drop the goto labels and the error message.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b · fixed in de33afc57f24538186bccf4c4f6c65dd38634fd8; From 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b · fixed in 1c1485343b7c1c39dab7ecb9cd16ba49fd0ce642; From 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b · fixed in 8db0a0fc84e80aa9924e0833aef6cc95df94e5a7; From 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b · fixed in 41e92e0caa1fe3df2efaca346bfcaeb7fb9826ab; From 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b · fixed in 0b30fbe6bf7cf6499b19dd886f466e7c9e820089; From 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b · fixed in 8fec16898f184e5f8f8fdd09ff1ced2bd7ffc13d; From 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b · fixed in 5ed1b048527bebe4529eb6e01c34dcc5d97ba5fe; From 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b · fixed in 2aaa41cf974f83a6fb105422bac4e2f107150774
- Linux Linux
4.19
- KernelLinux
From 4.19.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6
References 8
git.kernel.org
- stable/c/de33afc57f24538186bccf4c4f6c65dd38634fd8
- stable/c/1c1485343b7c1c39dab7ecb9cd16ba49fd0ce642
- stable/c/8db0a0fc84e80aa9924e0833aef6cc95df94e5a7
- stable/c/41e92e0caa1fe3df2efaca346bfcaeb7fb9826ab
- stable/c/0b30fbe6bf7cf6499b19dd886f466e7c9e820089
- stable/c/8fec16898f184e5f8f8fdd09ff1ced2bd7ffc13d
- stable/c/5ed1b048527bebe4529eb6e01c34dcc5d97ba5fe
- stable/c/2aaa41cf974f83a6fb105422bac4e2f107150774