Bug 1225087 (CVE-2021-47331) - VUL-0: CVE-2021-47331: kernel: usb: common: usb-conn-gpio: fix NULL pointer dereference of charger
Summary: VUL-0: CVE-2021-47331: kernel: usb: common: usb-conn-gpio: fix NULL pointer d...
Status: RESOLVED FIXED
Alias: CVE-2021-47331
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/406967/
Whiteboard: CVSSv3.1:SUSE:CVE-2021-47331:5.5:(AV:...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-23 08:48 UTC by SMASH SMASH
Modified: 2024-06-06 08:53 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-05-23 08:48:14 UTC 
In the Linux kernel, the following vulnerability has been resolved:

usb: common: usb-conn-gpio: fix NULL pointer dereference of charger

When power on system with OTG cable, IDDIG's interrupt arises before
the charger registration, it will cause a NULL pointer dereference,
fix the issue by registering the power supply before requesting
IDDIG/VBUS irq.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-47331
https://www.cve.org/CVERecord?id=CVE-2021-47331
https://git.kernel.org/stable/c/1a133a0996d6b4c83509d570ed4edcba34c44f25
https://git.kernel.org/stable/c/436906fd248e018403bcda61a9311d9af02912f1
https://git.kernel.org/stable/c/880287910b1892ed2cb38977893b947382a09d21
https://git.kernel.org/stable/c/8e8d910e9a3a7fba86140aff4924c30955ab228b
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2021/CVE-2021-47331.mbox
https://bugzilla.redhat.com/show_bug.cgi?id=2282429
Comment 2 Oliver Neukum 2024-06-06 08:48:25 UTC 
The driver was added in v5.10 and not backported to SLE12. There's nothing to do for us.
Comment 3 Andrea Mattiazzo 2024-06-06 08:53:52 UTC 
All done, closing.