Review reviewHigh

CVE-2023-53747

Linux

In the Linux kernel, the following vulnerability has been resolved: vc_screen: reload load of struct vc_data pointer in vcs_write() to avoid UAF After a call to console_unlock() in vcs_write() the vc_data struct can be freed by vc_port_destruct(). Because of that, the struct vc_data pointer must be reloaded in the while loop in vcs_write() after console_lock() to avoid a UAF when vcs_size() is called. Syzkaller reported a UAF in vcs_size(). BUG: KASAN: slab-use-after-free in vcs_size (drivers/tty/vt/vc_screen.c:215) Read of size 4 at addr ffff8880beab89a8 by task repro_vcs_size/4119 Call Tr...

CVSS
7.8
EPSS
0.14%
3.46% percentile
CISA KEV
Not listed
Published
2025.12.08
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.14%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: vc_screen: reload load of struct vc_data pointer in vcs_write() to avoid UAF After a call to console_unlock() in vcs_write() the vc_data struct can be freed by vc_port_destruct(). Because of that, the struct vc_data pointer must be reloaded in the while loop in vcs_write() after console_lock() to avoid a UAF when vcs_size() is called. Syzkaller reported a UAF in vcs_size(). BUG: KASAN: slab-use-after-free in vcs_size (drivers/tty/vt/vc_screen.c:215) Read of size 4 at addr ffff8880beab89a8 by task repro_vcs_size/4119 Call Tr...

Affected product and versions

Product
Linux
Affected versions
>= ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff < 934de9a9b659785fed3e820bc0c813a460c71fea, >= ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff < 0deff678157333d775af190f84696336cdcccd6d, >= ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff < a4e3c4c65ae8510e01352c9a4347e05c035b2ce2, >= ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff < 11dddfbb7a4e62489b01074d6c04d9d1b42e4047, >= ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff < e3d1adcad5b73c7ed0c7edb35ab68abcaa45cf67, >= ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff < 3338d0b9acde770ee588eead5cac32c25e7048fc, >= ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff < 1de42e7653d6714a7507ba6696151a1fa028c69f, >= ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff < 8fb9ea65c9d1338b0d2bb0a9122dc942cdd32357, >= 2.6.38
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available
CVE-2023-53747 — Linux | SECUFOCUS NOW