Bug 2284539 (CVE-2024-36905)
| Summary: | CVE-2024-36905 kernel: tcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV sockets | ||
|---|---|---|---|
| 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, allarkin, aquini, bhu, chwhite, cye, cyin, dbohanno, debarbos, dfreiber, drow, dvlasenk, eceliahudson36190, elonnmusk20k1, 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: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | kernel 4.19.314, kernel 5.4.276, kernel 5.10.217, kernel 5.15.159, kernel 6.1.91, kernel 6.6.31, kernel 6.8.10, kernel 6.9 | Doc Type: | If docs needed, set a value |
| Doc Text: | 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: | 2284540 | ||
| Bug Blocks: | 2284619 | ||
|
Description
Rohit Keshri
2024-06-03 13:05:03 UTC
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 2284540] The result of automatic check (that is developed by Alexander Larkin) for this CVE-2024-36905 is: CHECK Maybe valid. Check manually. with impact LOW (that is an approximation based on flags REMOTE KASAN DANGER INIT NETWORK SKB ; 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 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:9315 https://access.redhat.com/errata/RHSA-2024:9315 (In reply to Alex from comment #4) > The result of automatic check (that is developed by Alexander Larkin) for > this CVE-2024-36905 https://blockblast2.com is: CHECK Maybe valid. Check manually. with impact LOW > (that is an approximation based on flags REMOTE KASAN DANGER INIT NETWORK > SKB ; 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. What criteria are used to determine whether a CVE, such as CVE-2024-36905, is flagged as "Maybe valid" during the automatic check process, and how do the specific flags (REMOTE, KASAN, DANGER, INIT, NETWORK, SKB) influence this assessment? (In reply to Alex from comment #4) > The result of automatic check (that is developed by Alexander Larkin) for > this CVE-2024-36905 https://capybara-game.com is: CHECK Maybe valid. Check manually. with impact LOW > (that is an approximation based on flags REMOTE KASAN DANGER INIT NETWORK > SKB ; 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. Trying with REMOTE KASAN DANGER INIT NETWORK but information about it is a bit scarce. So results have to wait quite a while This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2025:2270 https://access.redhat.com/errata/RHSA-2025:2270 |