xenial/linux: 4.4.0-190.220 snap-debs snap:stlouis-kernel

Bug #1893418 reported by Kleber Sacilotto de Souza
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Released
Medium
Unassigned
Snap-certification-testing
In Progress
Medium
Canonical Hardware Certification
Snap-prepare
Fix Released
Medium
Canonical Kernel Team
Snap-release-to-beta
Fix Released
Medium
Canonical Kernel Team
Snap-release-to-candidate
New
Medium
Canonical Kernel Team
Snap-release-to-edge
Fix Released
Medium
Canonical Kernel Team
Snap-release-to-stable
New
Medium
Canonical Kernel Team

Bug Description

This bug will contain status and test results related to a kernel source (or snap) as stated in the title.

For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

-- swm properties --
kernel-stable-master-bug: 1893431
phase: Certification Testing
phase-changed: Wednesday, 02. September 2020 03:06 UTC
reason:
  snap-certification-testing: Ongoing -- testing in progress
snap-name: stlouis-kernel
variant: snap-debs

tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2020.08.31-1
description: updated
tags: added: kernel-sru-derivative-of-1893431
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in kernel-sru-workflow:
status: Confirmed → In Progress
summary: - xenial/linux: <version to be filled> snap-debs
+ xenial/linux: <version to be filled> snap-debs snap:stlouis-kernel
description: updated
summary: - xenial/linux: <version to be filled> snap-debs snap:stlouis-kernel
+ xenial/linux: 4.4.0-190.220 snap-debs snap:stlouis-kernel
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Stefan Bader (smb) wrote :

The cert testing seems to encounter some wireless issues and is kept in-progress for that reason.

Revision history for this message
Stefan Bader (smb) wrote :

The problems were isolated to the following commit:

ommit 2f864fcfb9b463d079a276d98ef604a3dc6a5311
Author: Dan Carpenter <email address hidden>
Date: Wed Jul 8 14:58:57 2020 +0300

    mwifiex: Prevent memory corruption handling keys

    BugLink: https://bugs.launchpad.net/bugs/1892822

    [ Upstream commit e18696786548244914f36ec3c46ac99c53df99c3 ]

    The length of the key comes from the network and it's a 16 bit number. It
    needs to be capped to prevent a buffer overflow.

    Fixes: 5e6e3a92b9a4 ("wireless: mwifiex: initial commit for Marvell mwifiex driver")

From what I understand the expectations are to receive a 16bit number. However the AP used in testing allow/use 32bit. Which gets clipped by the fixed kernel driver and then the association to the AP fails.

Andy Whitcroft (apw)
tags: removed: kernel-release-tracking-bug-live
Changed in kernel-sru-workflow:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.