Bug 2148458 (CVE-2022-3635) - CVE-2022-3635 kernel: use after in tst_timer in drivers/atm/idt77252.c
Summary: CVE-2022-3635 kernel: use after in tst_timer in drivers/atm/idt77252.c
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2022-3635
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2148459
TreeView+ depends on / blocked
 
Reported: 2022-11-25 14:49 UTC by Rohit Keshri
Modified: 2023-03-15 06:14 UTC (History)
51 users (show)

Fixed In Version: kernel 6.1 rc1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-08 18:15:56 UTC
Embargoed:

Attachments (Terms of Use)

Description Rohit Keshri 2022-11-25 14:49:11 UTC 
A vulnerability has been found in Linux Kernel in tst_timer in drivers/atm/idt77252.c of the component IPsec. The manipulation leads to use after free.

There are use-after-free bugs caused by tst_timer. The root cause
is that there are no functions to stop tst_timer in idt77252_exit().
One of the possible race conditions is shown below:

    (thread 1)          |        (thread 2)
                        |  idt77252_init_one
                        |    init_card
                        |      fill_tst
                        |        mod_timer(&card->tst_timer, ...)
idt77252_exit           |  (wait a time)
                        |  tst_timer
                        |
                        |    ...
  kfree(card) // FREE   |
                        |    card->soft_tst[e] // USE

The idt77252_dev is deallocated in idt77252_exit() and used in
timer handler.

Reference:
https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git/commit/?id=3f4093e2bf4673f218c0bf17d8362337c400e77b
Comment 2 Rohit Keshri 2022-11-25 15:08:11 UTC 
There was no shipped kernel version that was seen affected by this problem.
Comment 3 Product Security DevOps Team 2022-12-08 18:15:53 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-3635
Note You need to log in before you can comment on or make changes to this bug.