Bug 2262241 (CVE-2024-1151)
Summary: | CVE-2024-1151 kernel: stack overflow problem in Open vSwitch kernel module leading to DoS | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Rohit Keshri <rkeshri> |
Component: | vulnerability | Assignee: | Product Security <prodsec-ir-bot> |
Status: | NEW --- | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | acaringi, aconole, allarkin, aquini, bhu, carnil, chwhite, cye, cyin, dbohanno, debarbos, dfreiber, drow, dvlasenk, echaudro, ezulian, hkrzesin, jarod, jburrell, jdenham, jfaracco, jforbes, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, ldoskova, lgoncalv, lzampier, mleitner, mmilgram, mstowell, nmurray, ptalbert, rparrazo, rrobaina, rvrbovsk, rysulliv, scweaver, security-response-team, sukulkar, tglozar, tyberry, vkumar, wcosta, williams, wmealing, ycote, ykopkova, zhijwang |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | kernel 6.8-rc5 | Doc Type: | If docs needed, set a value |
Doc Text: |
A vulnerability was reported in the Open vSwitch sub-component in the Linux Kernel. The flaw occurs when a recursive operation of code push recursively calls into the code block. The OVS module does not validate the stack depth, pushing too many frames and causing a stack overflow. As a result, this can lead to a crash or other related issues.
|
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: | 2263738 | ||
Bug Blocks: | 2262238 |
Description
Rohit Keshri
2024-02-01 11:28:13 UTC
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 2263738] Is the "Fixed In Version" metadata really correct? The submitted change does not seem to have hit Linux tree yet and not in 6.8-rc4. (In reply to Salvatore Bonaccorso from comment #10) > Is the "Fixed In Version" metadata really correct? The submitted change does > not seem to have hit Linux tree yet and not in 6.8-rc4. Looks like it did not make rc4, it is still in linux-next. Hopefully rc5? In reply to comment #12: > (In reply to Salvatore Bonaccorso from comment #10) > > Is the "Fixed In Version" metadata really correct? The submitted change does > > not seem to have hit Linux tree yet and not in 6.8-rc4. > > Looks like it did not make rc4, it is still in linux-next. Hopefully rc5? Updated to kernel 6.8-rc5. Still need to check later if going to be included to rc5. |