Changelog in Linux kernel 6.12.1

 
hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer [+ + +]
Author: Hyunwoo Kim <[email protected]>
Date:   Wed Nov 6 04:36:04 2024 -0500

    hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer
    
    commit e629295bd60abf4da1db85b82819ca6a4f6c1e79 upstream.
    
    When hvs is released, there is a possibility that vsk->trans may not
    be initialized to NULL, which could lead to a dangling pointer.
    This issue is resolved by initializing vsk->trans to NULL.
    
    Signed-off-by: Hyunwoo Kim <[email protected]>
    Reviewed-by: Stefano Garzarella <[email protected]>
    Acked-by: Michael S. Tsirkin <[email protected]>
    Link: https://patch.msgid.link/Zys4hCj61V+mQfX2@v4bel-B760M-AORUS-ELITE-AX
    Signed-off-by: Jakub Kicinski <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>
 
Linux: Linux 6.12.1 [+ + +]
Author: Greg Kroah-Hartman <[email protected]>
Date:   Fri Nov 22 15:30:26 2024 +0100

    Linux 6.12.1
    
    Link: https://lore.kernel.org/r/[email protected]
    Tested-by: Mark Brown <[email protected]>
    Tested-by: SeongJae Park <[email protected]>
    Tested-by: Florian Fainelli <[email protected]>
    Tested-by: Shuah Khan <[email protected]>
    Tested-by: Ron Economos <[email protected]>
    Tested-by: Takeshi Ogasawara <[email protected]>
    Tested-by: Linux Kernel Functional Testing <[email protected]>
    Tested-by: Christian Heusel <[email protected]>
    Tested-by: Salvatore Bonaccorso <[email protected]>
    Tested-by: kernelci.org bot <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

 
media: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_format [+ + +]
Author: Benoit Sevens <[email protected]>
Date:   Thu Nov 7 14:22:02 2024 +0000

    media: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_format
    
    commit ecf2b43018da9579842c774b7f35dbe11b5c38dd upstream.
    
    This can lead to out of bounds writes since frames of this type were not
    taken into account when calculating the size of the frames buffer in
    uvc_parse_streaming.
    
    Fixes: c0efd232929c ("V4L/DVB (8145a): USB Video Class driver")
    Signed-off-by: Benoit Sevens <[email protected]>
    Cc: [email protected]
    Acked-by: Greg Kroah-Hartman <[email protected]>
    Reviewed-by: Laurent Pinchart <[email protected]>
    Signed-off-by: Hans Verkuil <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

 
mm/mmap: fix __mmap_region() error handling in rare merge failure case [+ + +]
Author: Liam R. Howlett <[email protected]>
Date:   Tue Nov 19 12:59:45 2024 -0500

    mm/mmap: fix __mmap_region() error handling in rare merge failure case
    
    The mmap_region() function tries to install a new vma, which requires a
    pre-allocation for the maple tree write due to the complex locking
    scenarios involved.
    
    Recent efforts to simplify the error recovery required the relocation of
    the preallocation of the maple tree nodes (via vma_iter_prealloc()
    calling mas_preallocate()) higher in the function.
    
    The relocation of the preallocation meant that, if there was a file
    associated with the vma and the driver call (mmap_file()) modified the
    vma flags, then a new merge of the new vma with existing vmas is
    attempted.
    
    During the attempt to merge the existing vma with the new vma, the vma
    iterator is used - the same iterator that would be used for the next
    write attempt to the tree.  In the event of needing a further allocation
    and if the new allocations fails, the vma iterator (and contained maple
    state) will cleaned up, including freeing all previous allocations and
    will be reset internally.
    
    Upon returning to the __mmap_region() function, the error is available
    in the vma_merge_struct and can be used to detect the -ENOMEM status.
    
    Hitting an -ENOMEM scenario after the driver callback leaves the system
    in a state that undoing the mapping is worse than continuing by dipping
    into the reserve.
    
    A preallocation should be performed in the case of an -ENOMEM and the
    allocations were lost during the failure scenario.  The __GFP_NOFAIL
    flag is used in the allocation to ensure the allocation succeeds after
    implicitly telling the driver that the mapping was happening.
    
    The range is already set in the vma_iter_store() call below, so it is
    not necessary and is dropped.
    
    Reported-by: [email protected]
    Closes: https://syzkaller.appspot.com/x/log.txt?x=17b0ace8580000
    Fixes: 5de195060b2e2 ("mm: resolve faulty mmap_region() error path behaviour")
    Signed-off-by: Liam R. Howlett <[email protected]>
    Reviewed-by: Vlastimil Babka <[email protected]>
    Reviewed-by: Lorenzo Stoakes <[email protected]>
    Cc: Jann Horn <[email protected]>
    Cc: <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>