🛡️ CVE-2024-46793 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

ASoC: Intel: Boards: Fix NULL pointer deref in BYT/CHT boards harder

In the Linux kernel, the following vulnerability has been resolved:

ASoC: Intel: Boards: Fix NULL pointer deref in BYT/CHT boards harder

Since commit 13f58267cda3 ("ASoC: soc.h: don't create dummy Component

via COMP_DUMMY()") dummy codecs declared like this:

SND_SOC_DAILINK_DEF(dummy,

DAILINK_COMP_ARRAY(COMP_DUMMY()));

expand to:

static struct snd_soc_dai_link_component dummy[] = {

};

Which means that dummy is a zero sized array and thus dais[i].codecs should

not be dereferenced *at all* since it points to the address of the next

variable stored in the data section as the "dummy" variable has an address

but no size, so even dereferencing dais[0] is already an out of bounds

array reference.

Which means that the if (dais[i].codecs->name) check added in

commit 7d99a70b6595 ("ASoC: Intel: Boards: Fix NULL pointer deref

in BYT/CHT boards") relies on that the part of the next variable which

the name member maps to just happens to be NULL.

Which apparently so far it usually is, except when it isn't

and then it results in crashes like this one:

[ 28.795659] BUG: unable to handle page fault for address: 0000000000030011

...

[ 28.795780] Call Trace:

[ 28.795787] <TASK>

...

[ 28.795862] ? strcmp+0x18/0x40

[ 28.795872] 0xffffffffc150c605

[ 28.795887] platform_probe+0x40/0xa0

...

[ 28.795979] ? __pfx_init_module+0x10/0x10 [snd_soc_sst_bytcr_wm5102]

Really fix things this time around by checking dais.num_codecs != 0.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2024-46793 is recorded against 2 packages.

  • kernel (from 6.8.0 up to 6.10.10)
  • linux-kernel

Timeline and source

Published on 18 September 2024 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2024-46793 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-09-18
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.8.0 6.10.10
linux-kernel

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-46793 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2024