CVE-2023-52907: nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame()
First published: Wed Aug 21 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame() Fix a use-after-free that occurs in hcd when in_urb sent from pn533_usb_send_frame() is completed earlier than out_urb. Its callback frees the skb data in pn533_send_async_complete() that is used as a transfer buffer of out_urb. Wait before sending in_urb until the callback of out_urb is called. To modify the callback of out_urb alone, separate the complete function of out_urb and ack_urb. Found by a modified version of syzkaller. BUG: KASAN: use-after-free in dummy_timer Call Trace: memcpy (mm/kasan/shadow.c:65) dummy_perform_transfer (drivers/usb/gadget/udc/dummy_hcd.c:1352) transfer (drivers/usb/gadget/udc/dummy_hcd.c:1453) dummy_timer (drivers/usb/gadget/udc/dummy_hcd.c:1972) arch_static_branch (arch/x86/include/asm/jump_label.h:27) static_key_false (include/linux/jump_label.h:207) timer_expire_exit (include/trace/events/timer.h:127) call_timer_fn (kernel/time/timer.c:1475) expire_timers (kernel/time/timer.c:1519) __run_timers (kernel/time/timer.c:1790) run_timer_softirq (kernel/time/timer.c:1803)
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=3.1<4.14.303 | |
| Linux Kernel | >=4.15<4.19.270 | |
| Linux Kernel | >=4.20<5.4.229 | |
| Linux Kernel | >=5.5<5.10.164 | |
| Linux Kernel | >=5.11<5.15.89 | |
| Linux Kernel | >=5.16<6.1.7 | |
| Linux Kernel | =6.2-rc1 | |
| Linux Kernel | =6.2-rc2 | |
| Linux Kernel | =6.2-rc3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/35529d6b827eedb6bf7e81130e4b7e0aba9e58d2
- https://git.kernel.org/stable/c/321db5131c92983dac4f3338e8fbb6df214238c0
- https://git.kernel.org/stable/c/9424d2205fe94a095fb9365ec0c6137f0b394a2b
- https://git.kernel.org/stable/c/0ca78c99656f5c448567db1e148367aa3b01c80a
- https://git.kernel.org/stable/c/39ae73e581112cfe27ba50aecb1c891ce57cecb1
- https://git.kernel.org/stable/c/8998db5021a28ad67aa8d627bdb4226e4046ccc4
- https://git.kernel.org/stable/c/9dab880d675b9d0dd56c6428e4e8352a3339371d
Frequently Asked Questions
What is the severity of CVE-2023-52907?
CVE-2023-52907 is rated as having a high severity due to the potential for a use-after-free vulnerability in the Linux kernel.
How do I fix CVE-2023-52907?
To fix CVE-2023-52907, update your Linux kernel to a version that includes the patch addressing this vulnerability.
Which versions of the Linux kernel are affected by CVE-2023-52907?
CVE-2023-52907 affects various versions of the Linux kernel from 3.1 up to and including 6.2-rc3.
What is the nature of the vulnerability described in CVE-2023-52907?
CVE-2023-52907 is a use-after-free vulnerability that can occur when specific USB operations are carried out.
Is CVE-2023-52907 a remote exploit risk?
CVE-2023-52907 could potentially be exploited locally, but it does not primarily represent a network-based exploit risk.
- agent/title
- agent/references
- agent/type
- agent/first-publish-date
- agent/description
- agent/author
- agent/event
- agent/remedy
- agent/severity
- agent/softwarecombine
- agent/weakness
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/linux
- canonical/linux kernel
- version/linux kernel/3.1
- version/linux kernel/4.15
- version/linux kernel/4.20
- version/linux kernel/5.5
- version/linux kernel/5.11
- version/linux kernel/5.16
- version/linux kernel/6.2-rc1
- version/linux kernel/6.2-rc2
- version/linux kernel/6.2-rc3