CVE-2024-53233

unicode: Fix utf8_load() error path

MEDIUM

5.5

CVSS Score

Published: December 27, 2024 at 01:50 PM UTC

Updated: June 17, 2026 at 08:08 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: unicode: Fix utf8_load() error path utf8_load() requests the symbol "utf8_data_table" and then checks if the requested UTF-8 version is supported. If it's unsupported, it tries to put the data table using symbol_put(). If an unsupported version is requested, symbol_put() fails like this: kernel BUG at kernel/module/main.c:786! RIP: 0010:__symbol_put+0x93/0xb0 Call Trace: <TASK> ? __die_body.cold+0x19/0x27 ? die+0x2e/0x50 ? do_trap+0xca/0x110 ? do_error_trap+0x65/0x80 ? __symbol_put+0x93/0xb0 ? exc_invalid_op+0x51/0x70 ? __symbol_put+0x93/0xb0 ? asm_exc_invalid_op+0x1a/0x20 ? __pfx_cmp_name+0x10/0x10 ? __symbol_put+0x93/0xb0 ? __symbol_put+0x62/0xb0 utf8_load+0xf8/0x150 That happens because symbol_put() expects the unique string that identify the symbol, instead of a pointer to the loaded symbol. Fix that by using such string.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

5.17 ≤ v < 6.1.1205.17 ≤ v < 6.11.115.17 ≤ v < 6.12.25.17 ≤ v < 6.135.17 ≤ v < 6.6.646.12 ≤ v < 6.12.26.2 ≤ v < 6.6.646.7 ≤ v < 6.11.112b3d047870120bcd46d7cc257d19ff49328fd5855.17

Vendor states this is fixed in 156bb2c569cd869583c593d27a5bd69e7b2a4264 (fixed)

Vendor states this is fixed in 4387cef540f36c2c9297460758cc2438305a24a0 (fixed)

Vendor states this is fixed in 6504dd27123966dc455494cb55217c04ca479121 (fixed)

Vendor states this is fixed in 89933f8ab3b4cad5ac14ea56a39947d1ffe7d0e3 (fixed)

Vendor states this is fixed in c4b6c1781f6cc4e2283120ac8d873864b8056f21 (fixed)

Vendor states this is fixed in 5.17 (unaffected)

Vendor states this is fixed in 6.1.120 (unaffected)

Vendor states this is fixed in 6.11.11 (unaffected)

Vendor states this is fixed in 6.12.2 (unaffected)

Vendor states this is fixed in 6.13 (unaffected)

Vendor states this is fixed in 6.6.64 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references