Attached is a debdiff for noble which fixes the problem. Note the patch
file has not been refreshed.
** Patch added: "Debdiff for systemd on noble"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2115391/+attachment/5886226/+files/lp2115391_noble.debdiff
--
You received this bug notif
the fix.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: systemd (Ubuntu Noble)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Also affects: systemd (Ubuntu Noble)
Importance: Undecided
Hi Christopher,
I understand that you really want this fixed, and it will get fixed, but we need
to do our testing properly to make sure we don't introduce any regressions.
The 5.15.0-144-generic kernel is in -proposed now. Could you please enable
-proposed and test it and make sure it works?
In
origin/master-next
commit 305625dd9cafef694d14ac89d0ae5e7da2022b7e
Author: Matthew Ruffell
Date: Wed May 14 09:39:22 2025 +0200
UBUNTU: SAUCE: Revert "btrfs: avoid unnecessary device path update for the
same device"
ubuntu-jammy$ git describe --contains 305625dd9cafef694d14ac89d0ae5e
Performing verification for noble.
I installed nginx 1.24.0-2ubuntu7.3 from -updates:
Running through the policy-rc.d testcase:
$ sudo vim /usr/sbin/policy-rc.d
#!/bin/sh
exit 0
$ sudo chmod 755 /usr/sbin/policy-rc.d
$ sudo apt install -y nginx
Reading package lists... Done
Building dependency
Performing verification for oracular.
I installed nginx 1.26.0-2ubuntu3.2 from -release:
Running through the policy-rc.d testcase:
$ sudo vim /usr/sbin/policy-rc.d
#!/bin/sh
exit 0
$ sudo chmod 755 /usr/sbin/policy-rc.d
$ sudo apt install -y nginx
Installing:
nginx
Inst
Performing verification for plucky.
I installed nginx 1.26.3-2ubuntu1 from -release:
Running through the policy-rc.d testcase:
$ sudo vim /usr/sbin/policy-rc.d
#!/bin/sh
exit 0
$ sudo chmod 755 /usr/sbin/policy-rc.d
$ sudo apt install -y nginx
Installing:
nginx
Installi
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Oracular)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Performing verification for focal:
We are going to perform a series of mounts and check if they work with a
patched vs unpatched kernel, and make sure all mounts work.
We will start with an unpatched kernel:
ubuntu@focal-dc:~$ uname -rv
5.4.0-216-generic #236-Ubuntu SMP Fri Apr 11 19:53:21 UTC
Well, that's all the verification done, more or less. I will now ask the
Security Team for release.
Removing the regression-update tag.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2112614
Title:
Performing verification for jammy:
We are going to perform a series of mounts and check if they work with a
patched vs unpatched kernel, and make sure all mounts work.
We will start with an unpatched kernel:
ubuntu@jammy-dc:~$ uname -rv
5.15.0-141-generic #151-Ubuntu SMP Sun May 18 21:35:19 UTC
Performing verification for noble:
We are going to perform a series of mounts and check if they work with a
patched vs unpatched kernel, and make sure all mounts work.
We will start with an unpatched kernel:
ubuntu@noble-dc:~$ uname -rv
6.8.0-60-generic #63-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr 15
Performing verification for oracular:
We are going to perform a series of mounts and check if they work with a
patched vs unpatched kernel, and make sure all mounts work.
We will start with an unpatched kernel:
$ uname -rv
6.11.0-26-generic #26-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 12 11:25:41 UTC
Performing verification for plucky:
We are going to perform a series of mounts and check if they work with a
patched vs unpatched kernel, and make sure all mounts work.
For plucky, all kernels are patched, so we are just going to check cifs-utils
with 6.14.0-15-generic.
I installed cifs-utils 2
I have verified all the memory leaks as being fixed in:
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/2113906
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2112614
Title:
Regression: Aft
Performing verification for focal.
I installed cifs-utils 2:6.9-1ubuntu0.3 from focal -updates.
Now, we can't run the full testcase for focal, as the kernel has a bug where
setns() fails due to getting a null / corrupted kerberos credential cache,
cifs-utils never takes the error paths, and valgr
** Changed in: cifs-utils (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: cifs-utils (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: cifs-utils (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: cifs-utils (Ubuntu Oracula
Performing verification for jammy.
I installed cifs-utils 2:6.14-1ubuntu0.2 from jammy -updates.
I followed the testcase and installed valgrind and moved the wrapper script
into place:
ubuntu@jammy-dc:~$ sudo mv /usr/sbin/cifs.upcall /usr/sbin/cifs.upcall.bin
ubuntu@jammy-dc:~$ sudo cp /usr/sbin
Performing verification for noble.
I installed cifs-utils 2:7.0-2ubuntu0.1 from noble -updates.
I followed the testcase and installed valgrind and moved the wrapper script
into place:
ubuntu@noble-dc:~$ sudo mv /usr/sbin/cifs.upcall /usr/sbin/cifs.upcall.bin
ubuntu@noble-dc:~$ sudo cp /usr/sbin/
Performing verification for oracular.
I installed cifs-utils 2:7.0-2.1ubuntu0.1 from oracular -updates.
I followed the testcase and installed valgrind and moved the wrapper script
into place:
ubuntu@oracular-dc:~$ sudo mv /usr/sbin/cifs.upcall /usr/sbin/cifs.upcall.bin
ubuntu@oracular-dc:~$ sudo
Performing verification for plucky.
I installed cifs-utils 2:7.2-2 from plucky -release.
I followed the testcase and installed valgrind and moved the wrapper script
into place:
ubuntu@plucky-dc:~$ sudo mv /usr/sbin/cifs.upcall /usr/sbin/cifs.upcall.bin
ubuntu@plucky-dc:~$ sudo cp /usr/sbin/cifs.
Questing has been fixed in 2:7.4-1, which has now reached the release
pocket.
For focal, jammy, noble, oracular and plucky, the changes have been
committed and the new packages are currently sitting in -security-
proposed:
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+pack
Fix released in questing with: 2:7.4-1
** Changed in: cifs-utils (Ubuntu Questing)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2113906
Title:
Regressi
Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105747
The debian maintainer has packaged 7.4 and released to debian -unstable,
and it has synced to questing -proposed, so questing is on track.
https://launchpad.net/ubuntu/+source/cifs-utils/2:7.4-1
I have finished testing all my
** Changed in: cifs-utils (Ubuntu Questing)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2113906
Title:
Regression: After LP2099917 cifs.upcall leaks memory on e
** Description changed:
[Impact]
There is a pretty minor memory leak in check_service_ticket_exists(), in the
order of about 56ish bytes give or take, caused by not freeing the error
messages introduced by bug 2099917.
-release: definitely lost: 0 bytes in 0 blocks
-security/-upd
** Description changed:
[Impact]
There is a pretty minor memory leak in check_service_ticket_exists(), in the
order of about 56ish bytes give or take, caused by not freeing the error
messages introduced by bug 2099917.
-release: definitely lost: 0 bytes in 0 blocks
-security/-upd
Debdiffs for this bug are over on the primary bug:
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/2112614
I won't fix questing, we will just sync the new release when it arrives
in debian.
** Description changed:
[Impact]
+
+ There is a pretty minor memory leak in check_service_tic
** Description changed:
[Impact]
Unfortunately, the release of CVE-2025-2312 caused a minor regression for some
users of cifs-utils, particularly those with AD users mounting shares from
non-standard UID numbers that aren't the default 0 or 1000.
Trying to mount a share with creden
It doesn't appear before I unlock my LUKS disk, but after I unlock, it
appears for a moment before gdm turns up. I don't think I have seen it
on shutdown yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Attached is a debdiff for noble which fixes this issue.
** Patch added: "Debdiff for cifs-utils on noble"
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/2112614/+attachment/5883409/+files/lp2112614_noble.debdiff
--
You received this bug notification because you are a member of Ub
Attached is a debdiff for plucky which fixes this issue.
** Patch added: "Debdiff for cifs-utils on plucky"
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/2112614/+attachment/5883407/+files/lp2112614_plucky.debdiff
--
You received this bug notification because you are a member of
Hi everyone,
The PPA now has test packages based on the above debdiffs with the upstreamed
fixes, and not the patch I was previously using / submitted.
I am going to need tomorrow to test this before I talk to the Security Team
to get this sponsored.
If you would like to help, you can install ci
Attached is a debdiff for focal which fixes this issue. Yes, I believe
this should go to focal primary -security and -updates pocket, and not
ESM.
** Patch added: "Debdiff for cifs-utils on focal"
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/2112614/+attachment/5883411/+files/lp21
Attached is a debdiff for jammy which fixes this issue.
** Patch added: "Debdiff for cifs-utils on jammy"
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/2112614/+attachment/5883410/+files/lp2112614_jammy.debdiff
--
You received this bug notification because you are a member of Ubu
Attached is a debdiff for oracular which fixes this issue.
** Patch added: "Debdiff for cifs-utils on oracular"
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/2112614/+attachment/5883408/+files/lp2112614_oracular.debdiff
--
You received this bug notification because you are a mem
Upstream mailing list discussion:
https://lore.kernel.org/linux-pci/20250611101442.387378-1-hui.w...@canonical.com/T/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2111521
Title:
nvme no longer dete
Regression bug: https://bugs.launchpad.net/ubuntu/+source/cifs-
utils/+bug/2113906
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099917
Title:
cifs.upcall: If kerberos credential cache already cont
Bug for the memory leak in error message if service principal doesn't
exist: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/2113906
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2112614
Tit
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: cifs-utils (Ubuntu Jammy)
Importance: High
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: cifs-utils (Ubuntu Noble)
Importance: High
Assignee: Matthew Ruffell (mruffell
Hi everyone,
Henrique Carvalho's fix has just been merged to upstream cifs-utils:
commit f4fd27cf60d6431d83ea18b4962aef845f9312bd
Author: Henrique Carvalho
Date: Fri May 30 12:28:14 2025 -0300
Subject: cifs.upcall: correctly treat UPTARGET_UNSPECIFIED as UPTARGET_APP
Link:
https://git.samba.o
The quirk doesn't work, well fancy that. That is very interesting to
know!
Thanks for testing Marks, it really helps cover a lot of the testing
matrix with the 6.11 hwe kernel, 6.15 mainline and the quirk patch.
Maybe we should write to upstream at this point and ask them for their
thoughts.
--
Hi everyone,
Again I really apologise for the regression, I am trying my best to push forward
a fix.
My contacts who suggested the initial fix have gone a bit silent, so I just
went ahead and submitted the patch upstream:
https://lore.kernel.org/linux-
cifs/20250610003259.19242-1-matthew.ruff...
Submitted to the Kernel Team mailing list:
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2025-June/160217.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2025-June/160218.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Description changed:
+ Subject: raid1: Fix NULL pointer de-reference in process_checks()
+
BugLink: https://bugs.launchpad.net/bugs/2112519
[Impact]
-
+ A null pointer dereference was found in raid1 during failure mode testing.
+ A raid1 array was set up, filled with data and a chec
Hi Ian,
Lets see if a quirk can fix it then. I built a new 6.8.0-60-generic kernel
with the following patch applied:
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index e18a67f288df..14188b99df54 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -5535,6 +5535,7 @@ DECLARE
Hi @info-tux-pc,
You mentioned workaround "1", does not work for you, this is ultimately
what I want to roll out to everyone, and I have tested it working
myself. Did you just install the test package?
Please note this package is NOT SUPPORTED by Canonical, and is for TESTING
PURPOSES ONLY. ONLY
Bug covering the regression:
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/2112614
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099914
Title:
CVE-2025-2312 cifs.upcall could access inc
mmediately.
** Affects: cifs-utils (Ubuntu)
Importance: High
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: cifs-utils (Ubuntu Focal)
Importance: High
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: cifs-uti
** Description changed:
[Impact]
During scalability tests where extreme load is generated by creating thousands
of VMs all at the same time, some VMs fail to get a DHCP lease and cannot be
pinged or sshed to after deployment.
The ovnmeta namespaces for networks that the VMs were cr
rtance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Fix Committed
** Affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: linux (Ubuntu Or
Yeah, it really does sound like "e259e3258f3f PCI: Wait for device
readiness with Configuration RRS".
Hui, will you build a test kernel based on 6.8.0-60-generic with that
one commit reverted?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Changed in: linux (Ubuntu Noble)
Status: Won't Fix => Fix Released
** Changed in: linux (Ubuntu Oracular)
Status: Won't Fix => Fix Released
** Changed in: linux (Ubuntu Plucky)
Status: Won't Fix => Fix Released
** Changed in: linux (Ubuntu Questing)
Status: Won't F
** Description changed:
[Impact]
- ovnmeta- namespaces are missing intermittently then can't reach to VMs.
+ During scalability tests where extreme load is generated by creating thousands
+ of VMs all at the same time, some VMs fail to get a DHCP lease and cannot be
+ pinged or sshed to after
Hi Stephane, or anyone else affected,
I have some test packages that contain the fix:
get_cachename_from_process_env((env_probe && (arg->upcall_target ==
UPTARGET_APP || arg->upcall_target == UPTARGET_UNSPECIFIED)) ? arg->pid
: 0);
in the following ppa:
https://launchpad.net/~mruffell/+archive/
Hi Stephane,
I am speaking with Bharath and other cifs-utils developers.
They are suggesting we can fix it with:
get_cachename_from_process_env((env_probe && (arg->upcall_target ==
UPTARGET_APP || arg->upcall_target == UPTARGET_UNSPECIFIED)) ? arg->pid
: 0);
I agree that it should fix the issue
Hi Stephane,
I sincerely apologise for causing this regression. I did try and cover all the
combinations with patched / unpatched kernel and patched / unpatched cifs-utils,
but it seems I missed this one.
It seems I only tested kerberos credential caches in the default locations,
and never hit th
Hi Christopher,
We got 2 ACKs from Senior Kernel Team members:
https://lists.ubuntu.com/archives/kernel-team/2025-May/159729.html
https://lists.ubuntu.com/archives/kernel-team/2025-May/159763.html
This should be accepted into the next SRU cycle.
The next step is for the kernel team to apply the
Attached is a debdiff for noble which fixes this issue V3
** Patch added: "Debdiff for nginx on noble V3"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2081308/+attachment/5880536/+files/lp2081308_noble_V3.debdiff
--
You received this bug notification because you are a member of Ubun
I have uploaded to N, O, P -unapproved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081308
Title:
Resolve circular dependency loop between nginx and nginx-common
To manage notifications about th
Attached is a debdiff for plucky which fixes this issue V2
** Patch added: "Debdiff for nginx on plucky V2"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2081308/+attachment/5880534/+files/lp2081308_plucky_V2.debdiff
--
You received this bug notification because you are a member of U
** Description changed:
[Impact]
If you use policy-rc.d to prevent unattended-upgrades from restarting your
services outside of a reboot or shutdown, it reveals a circular dependency
loop between nginx and nginx-common, where it cannot start nginx before
nginx-common is configured.
Attached is a debdiff for nginx on oracular that fixes this issue, V2
** Patch added: "Debdiff for nginx on oracular"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2081308/+attachment/5880530/+files/lp2081308_oracular_V2.debdiff
--
You received this bug notification because you are a
Attached is a debdiff for oracular which fixes this issue V3
** Patch added: "Debdiff for nginx on oracular V3"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2081308/+attachment/5880535/+files/lp2081308_oracular_V3.debdiff
--
You received this bug notification because you are a membe
Attached is a debdiff for noble which fixes this issue V2
** Description changed:
[Impact]
If you use policy-rc.d to prevent unattended-upgrades from restarting your
services outside of a reboot or shutdown, it reveals a circular dependency
loop between nginx and nginx-common, where it
Attached is a debdiff for plucky that fixes this issue.
** Patch removed: "Debdiff for nginx on noble"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2081308/+attachment/5855491/+files/lp2081308_noble.debdiff
** Patch added: "Debdiff for nginx on plucky"
https://bugs.launchpad.net/u
Performing verification for focal.
This will cover both the kernel and the cifs-utils package. both in
-proposed.
This is going to be long, as we need to test:
* patched kernel, patched cifs-utils
* patched kernel, existing cifs-utils
* existing kernel, patched cifs-utils
I started a fresh focal
Performing verification for jammy.
This will cover both the kernel and the cifs-utils package. both in
-proposed.
This is going to be long, as we need to test:
* patched kernel, patched cifs-utils
* patched kernel, existing cifs-utils
* existing kernel, patched cifs-utils
I started a fresh jammy
Performing verification for noble.
This will cover both the kernel and the cifs-utils package. both in
-proposed.
This is going to be long, as we need to test:
* patched kernel, patched cifs-utils
* patched kernel, existing cifs-utils
* existing kernel, patched cifs-utils
I started a fresh noble
Performing verification for oracular.
This will cover both the kernel and the cifs-utils package. both in
-proposed.
This is going to be long, as we need to test:
* patched kernel, patched cifs-utils
* patched kernel, existing cifs-utils
* existing kernel, patched cifs-utils
I started a fresh Or
Performing verification for focal.
I set up a fresh focal VM with the same reproducer as documented in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099914
The kernel is the latest 5.4.0-216-generic from -updates.
$ uname -rv
5.4.0-216-generic #236-Ubuntu SMP Fri Apr 11 19:53:21 UTC 202
Performing verification for jammy.
I set up a fresh jammy VM with the same reproducer as documented in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099914
The kernel is the latest 5.15.0-140-generic from -updates.
$ uname -rv
5.15.0-140-generic #150-Ubuntu SMP Sat Apr 12 06:00:09 UTC 2
Performing verification for noble.
I set up a fresh noble VM with the same reproducer as documented in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099914
The kernel is the latest 6.8.0-60-generic from -updates.
$ uname -rv
6.8.0-60-generic #63-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr 15 19:
Performing verification for Oracular.
I set up a fresh oracular VM with the same reproducer as documented in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099914
The kernel is the latest 6.11.0-26-generic from -updates.
$ uname -rv
6.11.0-26-generic #26-Ubuntu SMP PREEMPT_DYNAMIC Sat Ap
Packages are currently in -security-proposed:
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages?field.name_filter=cifs-
utils&field.status_filter=published&field.series_filter=
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Changed in: cifs-utils (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: cifs-utils (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: cifs-utils (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: cifs-utils (Ubuntu Oracula
Hi Ian,
Can you please make sure the modules and modules-extra packages are
installed?
$ sudo apt install linux-image-6.8.0-60-generic linux-
modules-6.8.0-60-generic linux-modules-extra-6.8.0-60-generic linux-
headers-6.8.0-60-generic
If they are, try regenerate your initramfs:
$ sudo update-i
Fix released in questing 1.26.3-3ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081308
Title:
Resolve circular dependency loop between nginx and nginx-common
To manage notifications about t
cky)
Importance: Undecided => Medium
** Changed in: nginx (Ubuntu Plucky)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: nginx (Ubuntu Oracular)
Status: Fix Committed => In Progress
** Changed in: nginx (Ubuntu Noble)
Status: Fix Committed => In Pr
We all have felt the frustration of evdi being out of tree for years
now, with constant breakage between the DRM subsystem and the evdi.ko
kernel module.
The best outcome would be to mainline the driver. There's a lot of
history behind it here:
https://github.com/DisplayLink/evdi/issues/25
The s
Hi Christopher,
I have written up a SRU template and submitted the revert to the Ubuntu
Kernel Team mailing list:
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2025-May/159630.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2025-May/159631.html
The next step is for the Ke
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffe
Vinicius Peixoto has submitted the kernel patches for -generic to the
Kernel
Team mailing list:
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2025-April/159465.html
Patches:
https://lists.ubuntu.com/archives/kernel-team/2025-April/159466.html
https://lists.ubuntu.com/archives/k
Debdiffs for this bug are over on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099914
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099917
Title:
cifs.upcall: If kerber
** Description changed:
[Impact]
- When mounting an SMB file share using the kernel client with Kerberos
+ When mounting an SMB file share using the kernel client with Kerberos
authentication, cifs.ko module makes an upcall to user space during the
session
setup phase to retrieve the Ke
** Summary changed:
- cifs.upcall program in the cifs-utils package fails to use a valid service
ticket from the credential cache if the TGT is expired or not exist
+ cifs.upcall: If kerberos credential cache already contains a valid service
ticket, use that even if TGT is expired
** Descriptio
For anything other than the main Ubuntu kernel for the release, just use
the upstream evdi repo. It is kept up to date for newer kernels, so use
this instead:
https://github.com/DisplayLink/evdi
You can zip it up and replace the evdi.tar.gz file in the DisplayLink
driver folder, if you unzip the
V2 debdiff which has been tidied up for sponsoring.
** Attachment added: "Tidied debdiff that will be sponsored"
https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/2023263/+attachment/5876631/+files/lp2023263_focal_v2.debdidff
--
You received this bug notification because you are a m
Okay Seyeong some feedback items:
The version is wrong, it needs to be 4.0.0-2ubuntu1.1 instead of
4.0.0-2ubuntu2. 2 could be taken by groovy etc and already used, so we
follow the security team versioning in
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
I would like
** Description changed:
- [ Impact ]
+ [Impact]
- A customer faced nrpe crash with Focal.
-
- Also they provided crashdump which has below.
-
- #3 0x7fbc5e7d82fc in malloc_printerr (str=str@entry=0x7fbc5e8f844d
- "corrupted size vs. prev_size") at malloc.c:5347
-
- #3 0x7fa2a22492f
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2099914
[Impact]
This is CVE-2025-2312, where namespace confusion by cifs.upcall may lead to
disclosing sensitive data from the host or container Kerberos credentials
cache
by accessing the wrong credential cache tha
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2099914
[Impact]
This is CVE-2025-2312, where namespace confusion by cifs.upcall may lead to
disclosing sensitive data from the host or container Kerberos credentials
cache
by accessing the wrong credential cache tha
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2099914
[Impact]
This is CVE-2025-2312, where namespace confusion by cifs.upcall may lead to
disclosing sensitive data from the host or container Kerberos credentials
cache
by accessing the wrong credential cache tha
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2099914
[Impact]
This is CVE-2025-2312, where namespace confusion by cifs.upcall may lead to
disclosing sensitive data from the host or container Kerberos credentials
cache
by accessing the wrong credential cache tha
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2099914
[Impact]
This is CVE-2025-2312, where namespace confusion by cifs.upcall may lead to
disclosing sensitive data from the host or container Kerberos credentials
cache
by accessing the wrong credential cache tha
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2099914
[Impact]
This is CVE-2025-2312, where namespace confusion by cifs.upcall may lead to
disclosing sensitive data from the host or container Kerberos credentials
cache
by accessing the wrong credential cache tha
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2099914
[Impact]
This is CVE-2025-2312, where namespace confusion by cifs.upcall may lead to
disclosing sensitive data from the host or container Kerberos credentials
cache
by accessing the wrong credential cache tha
Performing verification for Jammy and Noble.
Since there is no known synthetic reproducer for this, and we have had
success with the test kernel running in production, I just ran NFStest
(https://wiki.linux-nfs.org/wiki/index.php/NFStest) on both jammy with
5.15.0-138-generic and then 5.15.0-140-g
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2099914
[Impact]
This is CVE-2025-2312, where namespace confusion by cifs.upcall may lead to
disclosing sensitive data from the host or container Kerberos credentials
cache
by accessing the wrong credential cache tha
Hi Benjamin,
I am actually in the process of getting
commit 961b4b5e86bf56a2e4b567f81682defa5cba957e
From: Chuck Lever
Date: Fri, 26 Jan 2024 12:45:17 -0500
Subject: NFSD: Reset cb_seq_status after NFS4ERR_DELAY
Link:
https://github.com/torvalds/linux/commit/961b4b5e86bf56a2e4b567f81682defa5cba
1 - 100 of 1162 matches
Mail list logo
