[Bug 2144530] Re: Regression on Acer Nitro AN17-41: amdgpu DC/DMUB fails to light up internal eDP and Radeon-routed USB-C/DP outputs on Ubuntu 26.04 / kernel 6.19, while Ubuntu 24.04.4 live works

** Also affects: linux-firmware-amd-graphics (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: Triaged => Invalid ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: Invalid ** Also affects: linux-firmware (Ubuntu Resolute) Importance: Undecided Assignee: Leo Lin (0xff07) Status: Invalid ** Also affects: linux-firmware-amd-graphics (Ubuntu Resolute) Importance: Undecided Status: New ** Changed in: linux-firmware-amd-graphics (Ubuntu Resolute) Status: New => Fix Committed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2144530 Title: Regression on Acer Nitro AN17-41: amdgpu DC/DMUB fails to light up internal eDP and Radeon-routed USB-C/DP outputs on Ubuntu 26.04 / kernel 6.19, while Ubuntu 24.04.4 live works Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware-amd-graphics package in Ubuntu: Fix Committed Status in linux source package in Resolute: Invalid Status in linux-firmware source package in Resolute: Invalid Status in linux-firmware-amd-graphics source package in Resolute: Fix Committed Bug description: [ Impact ] here’s a regression reported by community in 1e2c1534: https://gitlab.freedesktop.org/drm/amd/-/work_items/5143#note_3411517 The last known good version is 43c969c1, and there’s a revert happening in upstream: https://gitlab.freedesktop.org/drm/amd/-/work_items/5143#note_3418637 [ Fix ] Cherry-pick the following revert commit: - d3a8c25 (amdgpu: Revert Yellow Carp DMUB fw to 0x4000045) Firmware in Noble and Questing currently doesn't include the bad version. Only Resolute needs this. [ Test ] Install the firmware package including this revert and boot. The display should light up normally. [ Where the problem could occur] Whatever was introduce after commit 43c969c1 would be reverted. Also, there's an ongoing SRU in Q and N to update the very same file in LP:#2147396. If it happens that they need firmware after commit 43c969c1 to fix the issue, then one of those 2 issues will likely not get fixed. ================= ORIGINAL DESCRIPTION ================= Problem summary =============== On an Acer Nitro AN17-41 laptop, Ubuntu 26.04 development branch with kernel 6.19.0-9-generic fails to display video when the internal panel and/or external USB-C display output are owned by the AMD iGPU. This appears to be a regression or behavior change in the newer Linux graphics stack, because the same machine and same monitor path work under: - Windows 11 - Ubuntu 24.04.4 live ISO The machine has: - Acer Nitro AN17-41 - BIOS V1.25 - AMD Rembrandt / Radeon 680M iGPU (1002:1681) - NVIDIA GeForce RTX 4050 Mobile / Max-Q dGPU (10de:28e1) I collected logs over SSH from another device in the failing cases because the machine was still alive even when both displays were black. Observed behavior on Ubuntu 26.04 / kernel 6.19 ================================================ When AMD owns the display outputs, the system boots but the displays stay black. This affects: - the internal eDP panel - an external monitor connected through the USB-C / DP output routed to Radeon The logs repeatedly show amdgpu DC / DMUB failures such as: - "Failed to enable ASSR" - "No reply for DMUB command: status=3" - "DMCUB error - collecting diagnostic data" - "Error queueing DMUB command: status=2" - "enabling link ... failed: 15" In the failing cases, DRM can still detect AMD-owned outputs as connected and enabled, but they remain black. Environment =========== OS: - Ubuntu 26.04 (Resolute Raccoon development branch) Kernel: - 6.19.0-9-generic Secure Boot: - enabled Hardware: - Acer Nitro AN17-41 - BIOS V1.25 - AMD Radeon 680M iGPU - NVIDIA RTX 4050 Mobile dGPU Regression evidence =================== I now have a working Linux control case on the same laptop and same physical USB-C monitor path. Tested with: - Ubuntu 24.04.4 LTS live ISO Results on Ubuntu 24.04.4: 1. Auto / hybrid mode:    - internal panel works    - external monitor connected to the Radeon-routed USB-C/DP output also works 2. NVIDIA GPU Only mode:    - internal panel works    - the same external monitor on the Radeon-routed USB-C/DP output also works in my test In both Ubuntu 24.04.4 test cases, the displays light up normally and I do not see the repeated amdgpu DC/DMUB failure pattern that appears on Ubuntu 26.04 / kernel 6.19. This strongly suggests: - the hardware is capable of driving both outputs under Linux - the Radeon-routed USB-C output is not fundamentally broken on this laptop - the issue is more likely a regression or missing quirk in the newer graphics/kernel stack used in Ubuntu 26.04 Additional control evidence =========================== The same USB-C monitor connected to the Radeon-routed USB-C output also works in Windows 11 when switching to Extend mode with Win+P. This further suggests that the physical hardware path is functional, and that the failing configuration is specific to the newer Linux graphics stack. What works ========== 1. NVIDIA GPU Only mode in firmware / BIOS on Ubuntu 26.04:    - the internal laptop panel works 2. Windows 11:    - the USB-C monitor connected to the Radeon-routed USB-C output works in Extend mode 3. Ubuntu 24.04.4 live ISO:    - Auto / hybrid mode works    - internal panel works    - Radeon-routed USB-C/DP external monitor works    - NVIDIA GPU Only mode also worked in my test, including the same USB-C monitor What does not work ================== On Ubuntu 26.04 / kernel 6.19: 1. Hybrid / normal mode:    - if the internal panel is owned by AMD, the panel stays black 2. AMD-only test:    - booting with      module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm    - internal eDP stays black    - external USB-C/DP monitor routed to Radeon also stays black This strongly suggests the issue is not caused by nvidia-drm handoff or by both DRM stacks loading together. How to reproduce ================ Case A: Hybrid / normal mode on Ubuntu 26.04 1. Boot Ubuntu 26.04 on Acer Nitro AN17-41. 2. Let the machine use its normal hybrid graphics routing. 3. If the internal panel is owned by AMD, the panel remains black. Case B: AMD-only test on Ubuntu 26.04 1. Boot with:    module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm 2. Connect an external monitor to the USB-C / DP output routed to Radeon before power-on. 3. Boot Ubuntu. 4. Result: both the internal panel and the external USB-C display remain black, although the system is alive and reachable over SSH. Case C: Verbose DRM logging on Ubuntu 26.04 1. Boot with:    drm.debug=0x1e log_buf_len=4M module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm 2. Result: same black screens, with detailed DRM / amdgpu logging showing DMUB / ASSR / link enable failures. Expected result =============== When AMD owns the internal eDP panel and/or Radeon-routed USB-C/DP output, the displays should light up normally and the system should reach a visible graphical session. Actual result ============= The system boots, but the displays stay black. Logs indicate failures in amdgpu DC / DMUB while trying to bring up AMD-owned display links. Important log patterns ====================== Examples consistently seen in the affected Ubuntu 26.04 boots: - "Skipping amdgpu DM backlight registration" - "Failed to get EDID from ACPI: -19" (seen in verbose DRM logging) - "boot timing validation failed ..." - "Failed to enable ASSR" - "No reply for DMUB command: status=3" - "DMCUB error - collecting diagnostic data" - "Error queueing DMUB command: status=2" - "enabling link 0 failed: 15" - "enabling link 2 failed: 15" Why I think this is a kernel/amdgpu issue ========================================= The issue reproduces when NVIDIA modules are blacklisted, so it does not appear to depend on nvidia-drm being active. The internal panel and the Radeon-routed external USB-C/DP output can both be detected as connected/enabled by DRM, but they still remain black. The same hardware and same USB-C path work: - on Windows 11 - on Ubuntu 24.04.4 live ISO This makes it look like an amdgpu DC / DMUB / link bring-up failure in the newer Ubuntu 26.04 graphics stack, rather than: - a simple EDID-not-found case - a generic Optimus/MUX problem - a pure backlight-only issue - a userspace / compositor-only issue - a fundamental hardware limitation of the laptop Tests already performed ======================= On Ubuntu 26.04: 1. Normal hybrid boot    - black internal display when AMD owns it 2. NVIDIA GPU Only mode    - internal panel works 3. AMD-only boot with:    module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm    - both internal eDP and Radeon-routed USB-C/DP stayed black 4. Verbose DRM boot with:    drm.debug=0x1e log_buf_len=4M    - same failure, more detailed DMUB / ASSR / link logs 5. Test with:    amdgpu.sg_display=0    - no improvement 6. Test with:    amdgpu.abmlevel=0    - no improvement On Ubuntu 24.04.4 live ISO: 7. Auto / hybrid mode    - internal panel works    - Radeon-routed USB-C/DP external monitor works 8. NVIDIA GPU Only mode    - internal panel works    - the same Radeon-routed USB-C/DP external monitor also worked in my test Attachments =========== I am attaching log bundles from these scenarios: - gpu-badboot4-nvidiablacklist.zip - gpu-badboot5-nvidiablacklistamdusbc.zip - gpu-badboot6-nvidiablacklistamdusbcdbg.zip - gpu-goodboot7-nvidiaonly-w-usbc-radeon.zip - gpu-badboot8-sgzero.zip - gpu-badboot9-abmzero.zip - gpu-goodboot10-u24044.zip - gpu-goodboot11-u24045.zip These include: - journalctl / dmesg output - DRM connector status and enabled state - lspci / module state - backlight info - EDID decode output - verbose DRM logs where applicable I can reproduce this reliably and I can collect additional logs over SSH because the machine stays alive even when both displays are black. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-6.19.0-9-generic 6.19.0-9.9 ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5 Uname: Linux 6.19.0-9-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC2: denixx 6079 F.... wireplumber  /dev/snd/controlC0: denixx 6079 F.... wireplumber  /dev/snd/controlC1: denixx 6079 F.... wireplumber  /dev/snd/seq: denixx 6059 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 16 08:26:28 2026 InstallationDate: Installed on 2026-03-15 (1 days ago) InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260313) IwDevWlp4s0Link: Not connected. MachineType: Acer Nitro AN17-41 ProcEnviron:  LANG=uk_UA.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color ProcFB:  0 amdgpudrmfb  1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.19.0-9-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2024 dmi.bios.release: 1.25 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Spacia_PEH dmi.board.vendor: RB dmi.board.version: V1.25 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000: dmi.product.family: Acer Nitro 17 dmi.product.name: Nitro AN17-41 dmi.product.sku: 0000000000000000 dmi.product.version: V1.25 dmi.sys.vendor: Acer --- ProblemType: Bug ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC2: ubuntu 4446 F.... wireplumber  /dev/snd/controlC0: ubuntu 4446 F.... wireplumber  /dev/snd/controlC1: ubuntu 4446 F.... wireplumber  /dev/snd/seq: ubuntu 4430 F.... pipewire CasperMD5CheckResult: pass CasperVersion: 26.04.0 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 IwDevWlp4s0Link: Not connected. LiveMediaBuild: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260316) MachineType: Acer Nitro AN17-41 NonfreeKernelModules: zfs Package: linux (not installed) ProcEnviron:  LANG=C.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB:  0 amdgpudrmfb  1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5 Tags: resolute wayland-session Uname: Linux 6.19.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 09/18/2024 dmi.bios.release: 1.25 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Spacia_PEH dmi.board.vendor: RB dmi.board.version: V1.25 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000: dmi.product.family: Acer Nitro 17 dmi.product.name: Nitro AN17-41 dmi.product.sku: 0000000000000000 dmi.product.version: V1.25 dmi.sys.vendor: Acer --- ProblemType: Bug ApportVersion: 2.33.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC2: ubuntu 4386 F.... wireplumber  /dev/snd/controlC0: ubuntu 4386 F.... wireplumber  /dev/snd/controlC1: ubuntu 4386 F.... wireplumber  /dev/snd/seq: ubuntu 4370 F.... pipewire CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CasperVersion: 26.04.1 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 IwDevWlp4s0Link: Not connected. LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260322) MachineType: Acer Nitro AN17-41 NonfreeKernelModules: zfs Package: linux (not installed) ProcEnviron:  LANG=C.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB:  0 amdgpudrmfb  1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash drm.debug=0x1e log_buf_len=4M ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3 Tags: resolute wayland-session Uname: Linux 7.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 09/18/2024 dmi.bios.release: 1.25 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Spacia_PEH dmi.board.vendor: RB dmi.board.version: V1.25 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:pfaAcerNitro17: dmi.product.family: Acer Nitro 17 dmi.product.name: Nitro AN17-41 dmi.product.sku: 0000000000000000 dmi.product.version: V1.25 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+subscriptions

[Bug 2148554] [NEW] Ubuntu 24.04, Noble, linux-bluefield-6.8: Fix refcount mishandling in vfio_pci_dma_buf functions

Public bug reported: SRU Justification: [IMPACT] A kernel NULL pointer dereference occurs on Nvidia BlueField DPUs running Ubuntu 24.04 (Noble) with linux-bluefield-6.8. The crash is triggered when closing a dma_buf file descriptor associated with a vfio_pci device. The root cause is that vfio_pci_dma_buf_release() and vfio_pci_dma_buf_cleanup() call vfio_put_device() to release a reference, but the reference was acquired with vfio_device_get(), which uses a separate refcount (device->refcount). Using vfio_put_device() incorrectly decrements the kobject refcount, triggering a refcount underflow and kernel crash. [FIX] Two custom patches are submitted: - UBUNTU: SAUCE: vfio: Export vfio device get and put registration helpers — exports vfio_device_try_get_registration and vfio_device_put_registration via EXPORT_SYMBOL_GPL in vfio_main.c and adds their declarations to vfio.h, making them available to other VFIO modules. - UBUNTU: SAUCE: vfio/pci: Use the correct ref count — fixes vfio_pci_dma_buf_release() and vfio_pci_dma_buf_cleanup() to call vfio_device_put_registration() instead of vfio_put_device(), correctly matching the reference acquisition done via vfio_device_get(). [TEST CASE] Compile tested on linux-bluefield-6.8 on the master-next branch. Functionally verified: the NULL pointer dereference no longer reproduces after applying the fix. [Regression Potential] Low. The change corrects an incorrect function call in the release path, and the fix has been functionally verified on the affected setup. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148554 Title: Ubuntu 24.04, Noble, linux-bluefield-6.8: Fix refcount mishandling in vfio_pci_dma_buf functions Status in linux package in Ubuntu: New Bug description: SRU Justification: [IMPACT] A kernel NULL pointer dereference occurs on Nvidia BlueField DPUs running Ubuntu 24.04 (Noble) with linux-bluefield-6.8. The crash is triggered when closing a dma_buf file descriptor associated with a vfio_pci device. The root cause is that vfio_pci_dma_buf_release() and vfio_pci_dma_buf_cleanup() call vfio_put_device() to release a reference, but the reference was acquired with vfio_device_get(), which uses a separate refcount (device->refcount). Using vfio_put_device() incorrectly decrements the kobject refcount, triggering a refcount underflow and kernel crash. [FIX] Two custom patches are submitted: - UBUNTU: SAUCE: vfio: Export vfio device get and put registration helpers — exports vfio_device_try_get_registration and vfio_device_put_registration via EXPORT_SYMBOL_GPL in vfio_main.c and adds their declarations to vfio.h, making them available to other VFIO modules. - UBUNTU: SAUCE: vfio/pci: Use the correct ref count — fixes vfio_pci_dma_buf_release() and vfio_pci_dma_buf_cleanup() to call vfio_device_put_registration() instead of vfio_put_device(), correctly matching the reference acquisition done via vfio_device_get(). [TEST CASE] Compile tested on linux-bluefield-6.8 on the master-next branch. Functionally verified: the NULL pointer dereference no longer reproduces after applying the fix. [Regression Potential] Low. The change corrects an incorrect function call in the release path, and the fix has been functionally verified on the affected setup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148554/+subscriptions

[Bug 1462173] Re: CVE-2015-4167

The task "linux-flo (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux-flo (Ubuntu) Status: New => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1462173 Title: CVE-2015-4167 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Expired Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Expired Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Expired Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Won't Fix Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Won't Fix Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Won't Fix Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-lts-xenial source package in Vivid: Won't Fix Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: Won't Fix Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in Vivid: Invalid Status in linux-snapdragon source package in Vivid: Won't Fix Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: Won't Fix Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: Won't Fix Status in linux-lts-backport-maverick source package in Wily: New Status in linux-lts-backport-natty source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: Won't Fix Status in linux-manta source package in Wily: Won't Fix Status in linux-mvl-dove source package in Wily: Invalid Status in linux-raspi2 source package in Wily: Invalid Status in linux-snapdragon source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-armadaxp source package in Xenial: Invalid Status in linux-ec2 source package in Xenial: Invalid Status in linux-flo source package in Xenial: Expired Status in linux-fsl-imx51 source package in Xenial: Invalid Status in linux-goldfish source package in Xenial: Expired Status in linux-lts-backport-maverick source package in Xenial: New Status in linux-lts-backport-natty source package in Xenial: New Status in linux-lts-quantal source package in Xenial: Invalid Status in linux-lts-raring source package in Xenial: Invalid Status in linux-lts-saucy source package in Xenial: Invalid Status in linux-lts-trusty source package in Xenial: Invalid Status in linux-lts-utopic source package in Xenial: Invalid Status in linux-lts-vivid source package in Xenial: Invalid Status in linux-lts-wily source package in Xenial: Invalid Status in linux-lts-xenial source package in Xenial: Invalid Status in linux-mako source package in Xenial: Expired Status in linux-manta source package in Xenial: Invalid Status in linux-mvl-dove source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: Fix Committed Status in linux-snapdragon source package in Xenial: Invalid Status in linux-ti-omap4 source package in Xenial: Invalid Status in linux source package in Yakkety: Invalid Status in linux-armadaxp source package in Yakkety: Invalid Status in linux-ec2 source package in Yakkety: Invalid Status in linux-flo source package in Yakkety: Won't Fix Status in linux-fsl-imx51 source package in Yakkety: Invalid Status in linux-goldfish source package in Yakkety: Won't Fix Status in linux-lts-backport-maverick source package in Yakkety: New Status in linux-lts-backport-natty source package in Yakkety: New Status in linux-lts-quantal source package in Yakkety: Invalid Status in linux-lts-raring source package in Yakkety: Invalid Status in linux-lts-saucy source package in Yakkety: Invalid Status in linux-lts-trusty source package in Yakkety: Invalid Status in linux-lts-utopic source package in Yakkety: Invalid Status in linux-lts-vivid source package in Yakkety: Invalid Status in linux-lts-wily source package in Yakkety: Invalid Status in linux-lts-xenial source package in Yakkety: Invalid Status in linux-mako source package in Yakkety: Won't Fix Status in linux-manta source package in Yakkety: Invalid Status in linux-mvl-dove source package in Yakkety: Invalid Status in linux-raspi2 source package in Yakkety: Fix Committed Status in linux-snapdragon source package in Yakkety: Invalid Status in linux-ti-omap4 source package in Yakkety: Invalid Bug description: The udf_read_inode function in fs/udf/inode.c in the Linux kernel before 3.19.1 does not validate certain length values, which allows local users to cause a denial of service (incorrect data representation or integer overflow, and OOPS) via a crafted UDF filesystem. Break-Fix: - 23b133bdc452aa441fcb9b82cbf6dd05cfd342d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462173/+subscriptions

[Bug 1077091] Re: CVE-2012-4565

The task "linux-lts-saucy (Ubuntu Wily)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life. If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Changed in: linux-lts-saucy (Ubuntu Wily) Status: New => Won't Fix -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1077091 Title: CVE-2012-4565 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Expired Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Won't Fix Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Expired Status in linux-lts-saucy package in Ubuntu: Expired Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Expired Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Won't Fix Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Won't Fix Status in linux-lts-saucy source package in Precise: Won't Fix Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Won't Fix Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Won't Fix Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Expired Status in linux-lts-saucy source package in Trusty: Expired Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux-lts-backport-oneiric source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Won't Fix Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: Invalid Status in linux-lts-backport-natty source package in Vivid: Won't Fix Status in linux-lts-backport-oneiric source package in Vivid: Invalid Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Won't Fix Status in linux-lts-saucy source package in Vivid: Won't Fix Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-lts-xenial source package in Vivid: Won't Fix Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in Vivid: Invalid Status in linux-snapdragon source package in Vivid: Won't Fix Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: Won't Fix Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: Invalid Status in linux-lts-backport-maverick source package in Wily: Invalid Status in linux-lts-backport-natty source package in Wily: Won't Fix Status in linux-lts-backport-oneiric source package in Wily: Invalid Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Won't Fix Status in linux-lts-saucy source package in Wily: Won't Fix Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: Won't Fix Status in linux-manta source package in Wily: Invalid Status in linux-mvl-dove source package in Wily: Invalid Status in linux-raspi2 source package in Wily: Invalid Status in linux-snapdragon source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-armadaxp source package in Xenial: Invalid Status in linux-ec2 source package in Xenial: Invalid Status in linux-flo source package in Xenial: Expired Status in linux-fsl-imx51 source package in Xenial: Invalid Status in linux-goldfish source package in Xenial: Invalid Status in linux-lts-backport-maverick source package in Xenial: Invalid Status in linux-lts-backport-natty source package in Xenial: Won't Fix Status in linux-lts-backport-oneiric source package in Xenial: Invalid Status in linux-lts-quantal source package in Xenial: Invalid Status in linux-lts-raring source package in Xenial: Expired Status in linux-lts-saucy source package in Xenial: Expired Status in linux-lts-trusty source package in Xenial: Invalid Status in linux-lts-utopic source package in Xenial: Invalid Status in linux-lts-vivid source package in Xenial: Invalid Status in linux-lts-wily source package in Xenial: Invalid Status in linux-lts-xenial source package in Xenial: Invalid Status in linux-mako source package in Xenial: Expired Status in linux-manta source package in Xenial: Invalid Status in linux-mvl-dove source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: Fix Committed Status in linux-snapdragon source package in Xenial: Invalid Status in linux-ti-omap4 source package in Xenial: Invalid Status in linux source package in Yakkety: Invalid Status in linux-armadaxp source package in Yakkety: Invalid Status in linux-ec2 source package in Yakkety: Invalid Status in linux-flo source package in Yakkety: Won't Fix Status in linux-fsl-imx51 source package in Yakkety: Invalid Status in linux-goldfish source package in Yakkety: Invalid Status in linux-lts-backport-maverick source package in Yakkety: Invalid Status in linux-lts-backport-natty source package in Yakkety: Won't Fix Status in linux-lts-backport-oneiric source package in Yakkety: Invalid Status in linux-lts-quantal source package in Yakkety: Invalid Status in linux-lts-raring source package in Yakkety: Won't Fix Status in linux-lts-saucy source package in Yakkety: Won't Fix Status in linux-lts-trusty source package in Yakkety: Invalid Status in linux-lts-utopic source package in Yakkety: Invalid Status in linux-lts-vivid source package in Yakkety: Invalid Status in linux-lts-wily source package in Yakkety: Invalid Status in linux-lts-xenial source package in Yakkety: Invalid Status in linux-mako source package in Yakkety: Won't Fix Status in linux-manta source package in Yakkety: Invalid Status in linux-mvl-dove source package in Yakkety: Invalid Status in linux-raspi2 source package in Yakkety: Fix Committed Status in linux-snapdragon source package in Yakkety: Invalid Status in linux-ti-omap4 source package in Yakkety: Invalid Status in linux-lts-backport-maverick source package in Hardy: Invalid Status in linux-lts-backport-natty source package in Hardy: Won't Fix Status in linux-lts-backport-oneiric source package in Hardy: Invalid Bug description: The tcp_illinois_info function in net/ipv4/tcp_illinois.c in the Linux kernel before 3.4.19, when the net.ipv4.tcp_congestion_control illinois setting is enabled, allows local users to cause a denial of service (divide-by-zero error and OOPS) by reading TCP stats. Break-Fix: - 8f363b77ee4fbf7c3bbcf5ec2c5ca482d396d664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1077091/+subscriptions

[Bug 1256094] Re: CVE-2013-6383

The task "linux-goldfish (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Changed in: linux-goldfish (Ubuntu) Status: New => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1256094 Title: CVE-2013-6383 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Expired Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Expired Status in linux-lts-backport-maverick package in Ubuntu: Won't Fix Status in linux-lts-backport-natty package in Ubuntu: Won't Fix Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Expired Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Won't Fix Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Fix Released Status in linux-lts-saucy source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Won't Fix Status in linux-lts-backport-natty source package in Quantal: Won't Fix Status in linux-lts-backport-maverick source package in Raring: Won't Fix Status in linux-lts-backport-natty source package in Raring: Won't Fix Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Won't Fix Status in linux-lts-backport-natty source package in Trusty: Won't Fix Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Won't Fix Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Won't Fix Status in linux-lts-backport-maverick source package in Vivid: Won't Fix Status in linux-lts-backport-natty source package in Vivid: Won't Fix Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-lts-xenial source package in Vivid: Won't Fix Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: Won't Fix Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in Vivid: Invalid Status in linux-snapdragon source package in Vivid: Won't Fix Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: Won't Fix Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: Won't Fix Status in linux-lts-backport-maverick source package in Wily: Won't Fix Status in linux-lts-backport-natty source package in Wily: Won't Fix Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: Won't Fix Status in linux-manta source package in Wily: Won't Fix Status in linux-mvl-dove source package in Wily: Invalid Status in linux-raspi2 source package in Wily: Invalid Status in linux-snapdragon source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-armadaxp source package in Xenial: Invalid Status in linux-ec2 source package in Xenial: Invalid Status in linux-flo source package in Xenial: Expired Status in linux-fsl-imx51 source package in Xenial: Invalid Status in linux-goldfish source package in Xenial: Expired Status in linux-lts-backport-maverick source package in Xenial: Won't Fix Status in linux-lts-backport-natty source package in Xenial: Won't Fix Status in linux-lts-quantal source package in Xenial: Invalid Status in linux-lts-raring source package in Xenial: Invalid Status in linux-lts-saucy source package in Xenial: Invalid Status in linux-lts-trusty source package in Xenial: Invalid Status in linux-lts-utopic source package in Xenial: Invalid Status in linux-lts-vivid source package in Xenial: Invalid Status in linux-lts-wily source package in Xenial: Invalid Status in linux-lts-xenial source package in Xenial: Invalid Status in linux-mako source package in Xenial: Expired Status in linux-manta source package in Xenial: Invalid Status in linux-mvl-dove source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: Fix Committed Status in linux-snapdragon source package in Xenial: Invalid Status in linux-ti-omap4 source package in Xenial: Invalid Status in linux source package in Yakkety: Invalid Status in linux-armadaxp source package in Yakkety: Invalid Status in linux-ec2 source package in Yakkety: Invalid Status in linux-flo source package in Yakkety: Won't Fix Status in linux-fsl-imx51 source package in Yakkety: Invalid Status in linux-goldfish source package in Yakkety: Won't Fix Status in linux-lts-backport-maverick source package in Yakkety: Won't Fix Status in linux-lts-backport-natty source package in Yakkety: Won't Fix Status in linux-lts-quantal source package in Yakkety: Invalid Status in linux-lts-raring source package in Yakkety: Invalid Status in linux-lts-saucy source package in Yakkety: Invalid Status in linux-lts-trusty source package in Yakkety: Invalid Status in linux-lts-utopic source package in Yakkety: Invalid Status in linux-lts-vivid source package in Yakkety: Invalid Status in linux-lts-wily source package in Yakkety: Invalid Status in linux-lts-xenial source package in Yakkety: Invalid Status in linux-mako source package in Yakkety: Won't Fix Status in linux-manta source package in Yakkety: Invalid Status in linux-mvl-dove source package in Yakkety: Invalid Status in linux-raspi2 source package in Yakkety: Fix Committed Status in linux-snapdragon source package in Yakkety: Invalid Status in linux-ti-omap4 source package in Yakkety: Invalid Bug description: The aac_compat_ioctl function in drivers/scsi/aacraid/linit.c in the Linux kernel before 3.11.8 does not require the CAP_SYS_RAWIO capability, which allows local users to bypass intended access restrictions via a crafted ioctl call. Break-Fix: - f856567b930dfcdbc3323261bf77240ccdde01f5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256094/+subscriptions

[Bug 1077091] Re: CVE-2012-4565

The task "linux-mako (Ubuntu Yakkety)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life. If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Changed in: linux-mako (Ubuntu Yakkety) Status: New => Won't Fix -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1077091 Title: CVE-2012-4565 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Expired Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Won't Fix Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Expired Status in linux-lts-saucy package in Ubuntu: Expired Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Expired Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Won't Fix Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Won't Fix Status in linux-lts-saucy source package in Precise: Won't Fix Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Won't Fix Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Won't Fix Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Expired Status in linux-lts-saucy source package in Trusty: Expired Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux-lts-backport-oneiric source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Won't Fix Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: Invalid Status in linux-lts-backport-natty source package in Vivid: Won't Fix Status in linux-lts-backport-oneiric source package in Vivid: Invalid Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Won't Fix Status in linux-lts-saucy source package in Vivid: Won't Fix Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-lts-xenial source package in Vivid: Won't Fix Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in Vivid: Invalid Status in linux-snapdragon source package in Vivid: Won't Fix Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: Won't Fix Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: Invalid Status in linux-lts-backport-maverick source package in Wily: Invalid Status in linux-lts-backport-natty source package in Wily: Won't Fix Status in linux-lts-backport-oneiric source package in Wily: Invalid Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Won't Fix Status in linux-lts-saucy source package in Wily: Won't Fix Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: Won't Fix Status in linux-manta source package in Wily: Invalid Status in linux-mvl-dove source package in Wily: Invalid Status in linux-raspi2 source package in Wily: Invalid Status in linux-snapdragon source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-armadaxp source package in Xenial: Invalid Status in linux-ec2 source package in Xenial: Invalid Status in linux-flo source package in Xenial: Expired Status in linux-fsl-imx51 source package in Xenial: Invalid Status in linux-goldfish source package in Xenial: Invalid Status in linux-lts-backport-maverick source package in Xenial: Invalid Status in linux-lts-backport-natty source package in Xenial: Won't Fix Status in linux-lts-backport-oneiric source package in Xenial: Invalid Status in linux-lts-quantal source package in Xenial: Invalid Status in linux-lts-raring source package in Xenial: Expired Status in linux-lts-saucy source package in Xenial: Expired Status in linux-lts-trusty source package in Xenial: Invalid Status in linux-lts-utopic source package in Xenial: Invalid Status in linux-lts-vivid source package in Xenial: Invalid Status in linux-lts-wily source package in Xenial: Invalid Status in linux-lts-xenial source package in Xenial: Invalid Status in linux-mako source package in Xenial: Expired Status in linux-manta source package in Xenial: Invalid Status in linux-mvl-dove source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: Fix Committed Status in linux-snapdragon source package in Xenial: Invalid Status in linux-ti-omap4 source package in Xenial: Invalid Status in linux source package in Yakkety: Invalid Status in linux-armadaxp source package in Yakkety: Invalid Status in linux-ec2 source package in Yakkety: Invalid Status in linux-flo source package in Yakkety: Won't Fix Status in linux-fsl-imx51 source package in Yakkety: Invalid Status in linux-goldfish source package in Yakkety: Invalid Status in linux-lts-backport-maverick source package in Yakkety: Invalid Status in linux-lts-backport-natty source package in Yakkety: Won't Fix Status in linux-lts-backport-oneiric source package in Yakkety: Invalid Status in linux-lts-quantal source package in Yakkety: Invalid Status in linux-lts-raring source package in Yakkety: Won't Fix Status in linux-lts-saucy source package in Yakkety: Won't Fix Status in linux-lts-trusty source package in Yakkety: Invalid Status in linux-lts-utopic source package in Yakkety: Invalid Status in linux-lts-vivid source package in Yakkety: Invalid Status in linux-lts-wily source package in Yakkety: Invalid Status in linux-lts-xenial source package in Yakkety: Invalid Status in linux-mako source package in Yakkety: Won't Fix Status in linux-manta source package in Yakkety: Invalid Status in linux-mvl-dove source package in Yakkety: Invalid Status in linux-raspi2 source package in Yakkety: Fix Committed Status in linux-snapdragon source package in Yakkety: Invalid Status in linux-ti-omap4 source package in Yakkety: Invalid Status in linux-lts-backport-maverick source package in Hardy: Invalid Status in linux-lts-backport-natty source package in Hardy: Won't Fix Status in linux-lts-backport-oneiric source package in Hardy: Invalid Bug description: The tcp_illinois_info function in net/ipv4/tcp_illinois.c in the Linux kernel before 3.4.19, when the net.ipv4.tcp_congestion_control illinois setting is enabled, allows local users to cause a denial of service (divide-by-zero error and OOPS) by reading TCP stats. Break-Fix: - 8f363b77ee4fbf7c3bbcf5ec2c5ca482d396d664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1077091/+subscriptions

[Bug 1395189] Re: CVE-2014-8989

The task "linux-lts-xenial (Ubuntu Vivid)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life. If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Changed in: linux-lts-xenial (Ubuntu Vivid) Status: New => Won't Fix -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1395189 Title: CVE-2014-8989 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Expired Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Expired Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Expired Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Won't Fix Status in linux-armadaxp source package in Precise: Won't Fix Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Won't Fix Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Won't Fix Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Won't Fix Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-lts-xenial source package in Vivid: Won't Fix Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: Won't Fix Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in Vivid: Invalid Status in linux-snapdragon source package in Vivid: Won't Fix Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: Won't Fix Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: Won't Fix Status in linux-lts-backport-maverick source package in Wily: New Status in linux-lts-backport-natty source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: Won't Fix Status in linux-manta source package in Wily: Won't Fix Status in linux-mvl-dove source package in Wily: Invalid Status in linux-raspi2 source package in Wily: Invalid Status in linux-snapdragon source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-armadaxp source package in Xenial: Invalid Status in linux-ec2 source package in Xenial: Invalid Status in linux-flo source package in Xenial: Expired Status in linux-fsl-imx51 source package in Xenial: Invalid Status in linux-goldfish source package in Xenial: Expired Status in linux-lts-backport-maverick source package in Xenial: New Status in linux-lts-backport-natty source package in Xenial: New Status in linux-lts-quantal source package in Xenial: Invalid Status in linux-lts-raring source package in Xenial: Invalid Status in linux-lts-saucy source package in Xenial: Invalid Status in linux-lts-trusty source package in Xenial: Invalid Status in linux-lts-utopic source package in Xenial: Invalid Status in linux-lts-vivid source package in Xenial: Invalid Status in linux-lts-wily source package in Xenial: Invalid Status in linux-lts-xenial source package in Xenial: Invalid Status in linux-mako source package in Xenial: Expired Status in linux-manta source package in Xenial: Invalid Status in linux-mvl-dove source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: Fix Committed Status in linux-snapdragon source package in Xenial: Invalid Status in linux-ti-omap4 source package in Xenial: Invalid Status in linux source package in Yakkety: Invalid Status in linux-armadaxp source package in Yakkety: Invalid Status in linux-ec2 source package in Yakkety: Invalid Status in linux-flo source package in Yakkety: Won't Fix Status in linux-fsl-imx51 source package in Yakkety: Invalid Status in linux-goldfish source package in Yakkety: Won't Fix Status in linux-lts-backport-maverick source package in Yakkety: New Status in linux-lts-backport-natty source package in Yakkety: New Status in linux-lts-quantal source package in Yakkety: Invalid Status in linux-lts-raring source package in Yakkety: Invalid Status in linux-lts-saucy source package in Yakkety: Invalid Status in linux-lts-trusty source package in Yakkety: Invalid Status in linux-lts-utopic source package in Yakkety: Invalid Status in linux-lts-vivid source package in Yakkety: Invalid Status in linux-lts-wily source package in Yakkety: Invalid Status in linux-lts-xenial source package in Yakkety: Invalid Status in linux-mako source package in Yakkety: Won't Fix Status in linux-manta source package in Yakkety: Invalid Status in linux-mvl-dove source package in Yakkety: Invalid Status in linux-raspi2 source package in Yakkety: Fix Committed Status in linux-snapdragon source package in Yakkety: Invalid Status in linux-ti-omap4 source package in Yakkety: Invalid Bug description: The Linux kernel through 3.17.4 does not properly restrict dropping of supplemental group memberships in certain namespace scenarios, which allows local users to bypass intended file permissions by leveraging a POSIX ACL containing an entry for the group category that is more restrictive than the entry for the other category, aka a "negative groups" issue, related to kernel/groups.c, kernel/uid16.c, and kernel/user_namespace.c. Break-Fix: - 273d2c67c3e179adb1e74f403d1e9a06e3f841b5 Break-Fix: - be7c6dba2332cef0677fbabb606e279ae76652c3 Break-Fix: - 80dd00a23784b384ccea049bfb3f259d3f973b9d Break-Fix: - f95d7918bd1e724675de4940039f2865e5eec5fe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1395189/+subscriptions

[Bug 1525152] Re: package linux-image-3.13.0-70-generic 3.13.0-70.113 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1525152 Title: package linux-image-3.13.0-70-generic 3.13.0-70.113 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: Expired Bug description: o sistema está travando, ficando inacesível. Precisa reiniciar o computador. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-70-generic 3.13.0-70.113 ProcVersionSignature: Ubuntu 3.13.0-70.113-generic 3.13.11-ckt29 Uname: Linux 3.13.0-70-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: lightdm 2554 F.... pulseaudio jadelino 3060 F.... pulseaudio /dev/snd/controlC0: lightdm 2554 F.... pulseaudio jadelino 3060 F.... pulseaudio Date: Fri Dec 11 08:10:32 2015 DuplicateSignature: package:linux-image-3.13.0-70-generic:3.13.0-70.113:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 InstallationDate: Installed on 2014-08-20 (477 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lo no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-70-generic root=/dev/sda5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.4 RfKill: SourcePackage: linux Title: package linux-image-3.13.0-70-generic 3.13.0-70.113 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLX:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525152/+subscriptions

[Bug 1786241] Re: Ubuntu 18.04.1 setup crashes on ACER Nitro AN515-42 laptop with AMD Ryzen 5 2400U processor

The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786241 Title: Ubuntu 18.04.1 setup crashes on ACER Nitro AN515-42 laptop with AMD Ryzen 5 2400U processor Status in linux package in Ubuntu: Expired Bug description: Got new notebook ACER Nitro AN515-42 with AMD Ryzen 5 2400U processor and Radeon Vega 8 Mobile Gfx. Original OS on SSD is Linpus Lite. uname -a# Linux 4.2.01p_mmc #5 SMP i686 athlon i386 GNU/Linux Linpus is running in text mode only. GRUB parameters are : kernel /boot/vmlinuz ro root= nolapic_timer loglevel=0 acpi_osi=Linux pcie_aspm=off acpi=copy_dsdt pci=nocrs irqpoll quiet I've decided to install UBUNTU MATE 18.04 on laptop. Image ubuntu-mate-18.04-desktop-amd64.iso had been downloaded and installed on flash drive with rufus. Laptop doesn't have a CD/DVD drive. Secure boot was switched off in BIOS and boot from flash drive was selected. I've selected UBUNTU try option in GRUB to test on my laptop. Boot of kernel fails with many similar messages on screen about "soft lockup - CPU#4 stuck for 23s". UBUNTU Mate install option had produced same error. I've installed Windows 10 trial to test the laptop - it is working good. I've downloaded BIOS update utility, which is for Windows 10 only, from ACER and I'd updated BIOS from v1.05 to v.1.08. No changes in Windows. The UBUNTU MATE setup still is making same errors. I've tested ubuntu-mate-16.04-desktop-amd64.iso and ubuntu-mate-18.04.1-desktop-amd64.iso with same errors. I've search WEB and found working solution for me with GRUB startup option "rcu_nocbs=0-7" cause my AMD got 4 cores/ 8 threads. Second error during installation is related to ACER BIOS ACPI. UBUNTU startup fails again. GRUB boot option acpi=off didn't work. GRUB boot options from original Linpus above didn't work. Found in WEB working solution for me with GRUB startup option ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 I've managed to install UBUNTU MATE 18.04.1 on my laptop. I've managed to install proprietary AMD driver 18.20 for Vega video chipset. GRUB boot options are "ro rcu_nocbs=0-7 ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 quiet splash vt.handoff=1". UBUNTU MAte is running but still is getting some errors and X freeze some time - I will make extra bug report. I'm reporting from my new laptop. Copy of LOG files are attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: romkuz 1576 F.... pulseaudio /dev/snd/controlC0: romkuz 1576 F.... pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=28e39be2-4c03-4cef-b100-37b42b56620b InstallationDate: Installed on 2018-08-07 (1 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Nitro AN515-42 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=d40acc90-785a-4efc-8b97-8060f5cad8c0 ro rcu_nocbs=0-7 ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip fax lpadmin netdev plugdev sambashare scanner sudo video _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Freed_RRS dmi.board.vendor: RR dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd05/23/2018:svnAcer:pnNitroAN515-42:pvrV1.08:rvnRR:rnFreed_RRS:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-42 dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786241/+subscriptions

[Bug 1549203] Re: CVE-2016-2550

The task "linux-goldfish (Ubuntu Xenial)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Changed in: linux-goldfish (Ubuntu Xenial) Status: New => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1549203 Title: CVE-2016-2550 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Expired Status in linux-goldfish package in Ubuntu: Expired Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Expired Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Won't Fix Status in linux-armadaxp source package in Vivid: Won't Fix Status in linux-flo source package in Vivid: Won't Fix Status in linux-goldfish source package in Vivid: Won't Fix Status in linux-lts-quantal source package in Vivid: Won't Fix Status in linux-lts-raring source package in Vivid: Won't Fix Status in linux-lts-saucy source package in Vivid: Won't Fix Status in linux-lts-trusty source package in Vivid: Won't Fix Status in linux-lts-utopic source package in Vivid: Won't Fix Status in linux-lts-vivid source package in Vivid: Won't Fix Status in linux-lts-wily source package in Vivid: Won't Fix Status in linux-lts-xenial source package in Vivid: Won't Fix Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: Won't Fix Status in linux-raspi2 source package in Vivid: Won't Fix Status in linux-snapdragon source package in Vivid: Won't Fix Status in linux-ti-omap4 source package in Vivid: Won't Fix Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: Won't Fix Status in linux-goldfish source package in Wily: Won't Fix Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: Won't Fix Status in linux-manta source package in Wily: Won't Fix Status in linux-raspi2 source package in Wily: Fix Released Status in linux-snapdragon source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-armadaxp source package in Xenial: Invalid Status in linux-flo source package in Xenial: Expired Status in linux-goldfish source package in Xenial: Expired Status in linux-lts-quantal source package in Xenial: Invalid Status in linux-lts-raring source package in Xenial: Invalid Status in linux-lts-saucy source package in Xenial: Invalid Status in linux-lts-trusty source package in Xenial: Invalid Status in linux-lts-utopic source package in Xenial: Invalid Status in linux-lts-vivid source package in Xenial: Invalid Status in linux-lts-wily source package in Xenial: Invalid Status in linux-lts-xenial source package in Xenial: Invalid Status in linux-mako source package in Xenial: Expired Status in linux-manta source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: Invalid Status in linux-snapdragon source package in Xenial: Invalid Status in linux-ti-omap4 source package in Xenial: Invalid Status in linux source package in Yakkety: Won't Fix Status in linux-armadaxp source package in Yakkety: Invalid Status in linux-flo source package in Yakkety: Won't Fix Status in linux-goldfish source package in Yakkety: Won't Fix Status in linux-lts-quantal source package in Yakkety: Invalid Status in linux-lts-raring source package in Yakkety: Invalid Status in linux-lts-saucy source package in Yakkety: Invalid Status in linux-lts-trusty source package in Yakkety: Invalid Status in linux-lts-utopic source package in Yakkety: Invalid Status in linux-lts-vivid source package in Yakkety: Invalid Status in linux-lts-wily source package in Yakkety: Invalid Status in linux-lts-xenial source package in Yakkety: Invalid Status in linux-mako source package in Yakkety: Won't Fix Status in linux-manta source package in Yakkety: Invalid Status in linux-raspi2 source package in Yakkety: Invalid Status in linux-snapdragon source package in Yakkety: Invalid Status in linux-ti-omap4 source package in Yakkety: Invalid Bug description: The Linux kernel before 4.5 allows local users to bypass file- descriptor limits and cause a denial of service (memory consumption) by leveraging incorrect tracking of descriptor ownership and sending each descriptor over a UNIX socket before closing it. NOTE: this vulnerability exists because of an incorrect fix for CVE-2013-4312. Break-Fix: 712f4aad406bb1ed67f3f98d04c044191f0ff593 415e3d3e90ce9e18727e8843ae343eda5a58fad6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1549203/+subscriptions