CVE-2023-53747: vc_screen: reload load of struct vc_data pointer in vcs_write() to avoid UAF
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0deff678157333d775af190f84696336cdcccd6d, 11dddfbb7a4e62489b01074d6c04d9d1b42e4047, 1de42e7653d6714a7507ba6696151a1fa028c69f.
Low priority for now. Upgrade to Linux Linux 0deff678157333d775af190f84696336cdcccd6d, 11dddfbb7a4e62489b01074d6c04d9d1b42e4047, 1de42e7653d6714a7507ba6696151a1fa028c69f or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 Trace: <TASK> __asan_report_load4_noabort (mm/kasan/report_generic.c:380) vcs_size (drivers/tty/vt/vc_screen.c:215) vcs_write (drivers/tty/vt/vc_screen.c:664) vfs_write (fs/read_write.c:582 fs/read_write.c:564) ... <TASK> Allocated by task 1213: kmalloc_trace (mm/slab_common.c:1064) vc_allocate (./include/linux/slab.h:559 ./include/linux/slab.h:680 drivers/tty/vt/vt.c:1078 drivers/tty/vt/vt.c:1058) con_install (drivers/tty/vt/vt.c:3334) tty_init_dev (drivers/tty/tty_io.c:1303 drivers/tty/tty_io.c:1415 drivers/tty/tty_io.c:1392) tty_open (drivers/tty/tty_io.c:2082 drivers/tty/tty_io.c:2128) chrdev_open (fs/char_dev.c:415) do_dentry_open (fs/open.c:921) vfs_open (fs/open.c:1052) ... Freed by task 4116: kfree (mm/slab_common.c:1016) vc_port_destruct (drivers/tty/vt/vt.c:1044) tty_port_destructor (drivers/tty/tty_port.c:296) tty_port_put (drivers/tty/tty_port.c:312) vt_disallocate_all (drivers/tty/vt/vt_ioctl.c:662 (discriminator 2)) vt_ioctl (drivers/tty/vt/vt_ioctl.c:903) tty_ioctl (drivers/tty/tty_io.c:2778) ... The buggy address belongs to the object at ffff8880beab8800 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 424 bytes inside of freed 1024-byte region [ffff8880beab8800, ffff8880beab8c00) The buggy address belongs to the physical page: page:00000000afc77580 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0xbeab8 head:00000000afc77580 order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 flags: 0xfffffc0010200(slab|head|node=0|zone=1|lastcpupid=0x1fffff) page_type: 0xffffffff() raw: 000fffffc0010200 ffff888100042dc0 ffffea000426de00 dead000000000002 raw: 0000000000000000 0000000000100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff8880beab8880: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff8880beab8900: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb >ffff8880beab8980: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff8880beab8a00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff8880beab8a80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ================================================================== Disabling lock debugging due to kernel taint
- Published
- Dec 8, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.38affected
- ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff and later · before 934de9a9b659785fed3e820bc0c813a460c71feaaffected · git
- ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff and later · before 0deff678157333d775af190f84696336cdcccd6daffected · git
- ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff and later · before a4e3c4c65ae8510e01352c9a4347e05c035b2ce2affected · git
- ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff and later · before 11dddfbb7a4e62489b01074d6c04d9d1b42e4047affected · git
- ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff and later · before e3d1adcad5b73c7ed0c7edb35ab68abcaa45cf67affected · git
- ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff and later · before 3338d0b9acde770ee588eead5cac32c25e7048fcaffected · git
- ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff and later · before 1de42e7653d6714a7507ba6696151a1fa028c69faffected · git
- ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff and later · before 8fb9ea65c9d1338b0d2bb0a9122dc942cdd32357affected · git
- before 2.6.38not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40326Dec 8, 2025 · NFSD: Define actions for the new time_deleg FATTR4 attributes30Monitor
- ← EarlierCVE-2022-50630Dec 8, 2025 · mm: hugetlb: fix UAF in hugetlb_handle_userfault31Monitor
- Later →CVE-2023-53750Dec 8, 2025 · pinctrl: freescale: Fix a memory out of bounds when num_configs is 10Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0deff678157333d775af190f84696336cdcccd6d | Vendor (CNA) |
| Linux Linux | 11dddfbb7a4e62489b01074d6c04d9d1b42e4047 | Vendor (CNA) |
| Linux Linux | 1de42e7653d6714a7507ba6696151a1fa028c69f | Vendor (CNA) |
| Linux Linux | 3338d0b9acde770ee588eead5cac32c25e7048fc | Vendor (CNA) |
| Linux Linux | 8fb9ea65c9d1338b0d2bb0a9122dc942cdd32357 | Vendor (CNA) |
| Linux Linux | 934de9a9b659785fed3e820bc0c813a460c71fea | Vendor (CNA) |
| Linux Linux | a4e3c4c65ae8510e01352c9a4347e05c035b2ce2 | Vendor (CNA) |
| Linux Linux | e3d1adcad5b73c7ed0c7edb35ab68abcaa45cf67 | Vendor (CNA) |
| debian:linux | 6.1.37-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/11dddfbb7a4e62489b01074d6c04d9d1b42e4047
- git.kernel.org/stable/c/1de42e7653d6714a7507ba6696151a1fa028c69f
- git.kernel.org/stable/c/3338d0b9acde770ee588eead5cac32c25e7048fc
- git.kernel.org/stable/c/8fb9ea65c9d1338b0d2bb0a9122dc942cdd32357
- git.kernel.org/stable/c/934de9a9b659785fed3e820bc0c813a460c71fea
- git.kernel.org/stable/c/a4e3c4c65ae8510e01352c9a4347e05c035b2ce2
- git.kernel.org/stable/c/e3d1adcad5b73c7ed0c7edb35ab68abcaa45cf67
Vendor advisories and official records. Exploit/PoC links are deliberately left out.