Bug 1195329 - (CVE-2022-0400) VUL-0: CVE-2022-0400: kernel-source-rt,kernel-source,kernel-source-azure: Out of bounds read in the smc protocol stack
(CVE-2022-0400)
VUL-0: CVE-2022-0400: kernel-source-rt,kernel-source,kernel-source-azure: Out...
Status: RESOLVED INVALID
Classification: Novell Products
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents
unspecified
Other Other
: P3 - Medium : Normal
: ---
Assigned To: Security Team bot
Security Team bot
https://smash.suse.de/issue/321944/
CVSSv3.1:SUSE:CVE-2022-0400:5.9:(AV:N...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-01-31 10:24 UTC by Robert Frohl
Modified: 2022-06-07 07:17 UTC (History)
6 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Frohl 2022-01-31 10:24:11 UTC
rh#2044575

A out-of-bounds read vulnerability in the smc protocol stack in the Linux kernel.

References:

https://bugzilla.redhat.com/show_bug.cgi?id=2040604

References:
https://bugzilla.redhat.com/show_bug.cgi?id=2044575
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400
Comment 6 Petr Tesařík 2022-06-07 05:05:05 UTC
On a second thought, I am *NOT* referencing CVE-2022-0400 in the backport of c0bf3d8a943b. RH bug 2044575 gives credit to Ziming Zhang (this must be zhangziming.zzm@antgroup.com), but there is no upstream smc commit with his name or email, so the suspected vulnerability has most likely turned out to be a non-issue.

I'm re-assigning back to the Security Team for the final decision whether this bug should be closed as INVALID.
Comment 7 Thomas Leroy 2022-06-07 07:17:24 UTC
(In reply to Petr Tesařík from comment #6)
> On a second thought, I am *NOT* referencing CVE-2022-0400 in the backport of
> c0bf3d8a943b. RH bug 2044575 gives credit to Ziming Zhang (this must be
> zhangziming.zzm@antgroup.com), but there is no upstream smc commit with his
> name or email, so the suspected vulnerability has most likely turned out to
> be a non-issue.
> 
> I'm re-assigning back to the Security Team for the final decision whether
> this bug should be closed as INVALID.

Thanks Petr for your investigations. Closing as INVALID