Bug 2277840 (CVE-2022-48632)
Summary: | CVE-2022-48632 kernel: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Zack Miele <zmiele> |
Component: | vulnerability | Assignee: | Product Security <prodsec-ir-bot> |
Status: | NEW --- | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | acaringi, allarkin, aquini, bhu, chwhite, cye, cyin, dbohanno, debarbos, dfreiber, drow, dvlasenk, esandeen, ezulian, hkrzesin, jarod, jburrell, jdenham, jfaracco, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, ldoskova, lgoncalv, lzampier, mleitner, mmilgram, mstowell, nmurray, ptalbert, rparrazo, rrobaina, rvrbovsk, rysulliv, scweaver, sidakwo, sukulkar, tglozar, tyberry, vkumar, wcosta, williams, wmealing, ycote, ykopkova, zhijwang |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | Flags: | mmilgram:
needinfo?
(allarkin) |
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | kernel 5.10.146, kernel 5.15.71, kernel 5.19.12, kernel 6.0 | Doc Type: | If docs needed, set a value |
Doc Text: |
A flaw was found in the Linux kernel. The following vulnerability has been resolved: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction().
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2277879 |
Description
Zack Miele
2024-04-29 16:22:25 UTC
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2022-48632 is: CHECK Maybe valid. Check manually. with impact LOW (that is an approximation based on flags OOB USB SIMPLEFIX ; these flags parsed automatically based on patch data). Such automatic check happens only for Low/Moderates (and only when not from reporter, but parsing already existing CVE). Highs always checked manually (I check it myself and then we check it again in Remediation team). In rare cases some of the Moderates could be increased to High later. This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:5102 https://access.redhat.com/errata/RHSA-2024:5102 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:5101 https://access.redhat.com/errata/RHSA-2024:5101 |