View Issue Details

IDProjectCategoryView StatusLast Update
0004288Kali LinuxGeneral Bugpublic2017-10-06 08:13
Reportersteev Assigned Tosteev  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionwon't fix 
Product Version2017.2 
Summary0004288: kernel division by zero bug
Description

This hasn't been backported yet, however upstream kernel has https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5ccba44ba118a5000cccc50076b0344632459779

We are affected by the same issue, including in the latest kernel that was uploaded to kali-rolling yesterday

Additional Information

We should make sure that patch is rolled in to our next kernel update - it has not been back ported to 4.12 yet upstream that I can see, but has been slated for 4.13 in the stable-queue git repo on kernel.org

Activities

steev

steev

2017-10-04 14:11

manager   ~0007468

apt show linux-image-4.12.0

Package: linux-image-4.12.0-kali2-amd64
Version: 4.12.13-1kali2
Priority: optional
Section: kernel
Source: linux
Maintainer: Kali Developers <[email protected]>
Installed-Size: 193 MB

rhertzog

rhertzog

2017-10-04 16:57

administrator   ~0007469

Why is this fix urgent? It's not like it's a common operation to run "sysctl kernel.sched_time_avg_ms=0". Linux 4.13 is already in unstable so it should come in the not-to-far future.

steev

steev

2017-10-04 17:05

manager   ~0007470

I listed the priority as normal, not urgent.

But anyone with root access can run the command which causes a denial of service on the machine because it immediately crashes.

steev

steev

2017-10-04 17:06

manager   ~0007471

Also, it's still in the queue for 4.13, it's not in 4.13 yet.

rhertzog

rhertzog

2017-10-04 17:13

administrator   ~0007472

Anyone with root access can shutdown the machine, delete all the files, etc. :-)

What I wanted to say is that I don't see the need to track this in Kali, it will come in due time with a new kernel release but it doesn't matter much if it's in the next update or the one after for instance.

steev

steev

2017-10-06 08:13

manager   ~0007480

I agree, I just don't like allowing things that allow users to shoot themselves in the foot. It's a minor change that stops something as simple as a typo when making a change from crashing the system. That said, I'm gonna close the bug since the fix will get in eventually.

Issue History

Date Modified Username Field Change
2017-10-04 14:02 steev New Issue
2017-10-04 14:11 steev Note Added: 0007468
2017-10-04 16:57 rhertzog Note Added: 0007469
2017-10-04 17:05 steev Note Added: 0007470
2017-10-04 17:06 steev Note Added: 0007471
2017-10-04 17:13 rhertzog Note Added: 0007472
2017-10-06 08:13 steev Assigned To => steev
2017-10-06 08:13 steev Status new => closed
2017-10-06 08:13 steev Resolution open => won't fix
2017-10-06 08:13 steev Note Added: 0007480