Hmm, maybe it's because I'm tired, but I've found something strange? If you take a look at http://sunsite.icm.edu.pl/pub/Linux/...slackware64/a/ You'll find there the following kernel packages:

+ kernel-generic-3.10.17-x86_64-3.txz
+ kernel-huge-3.10.17-x86_64-3.txz
+ kernel-modules-3.10.17-x86_64-3.txz

As you can see, all packages are v. 3.10.17 and BUILD 3 (three), created on 23-Oct-2013. That's OK, but why is a newer (14-Feb-2014!) BUILD 2 (two) in patches?!?

http://sunsite.icm.edu.pl/pub/Linux/...nux-3.10.17-2/

+ kernel-generic-3.10.17-x86_64-2.txz
+ kernel-huge-3.10.17-x86_64-2.txz
+ kernel-modules-3.10.17-x86_64-2.txz

Why is build 2 (and not 4) in patches?

Looks like a mistake to me. There was a kernel security patch for 64-bit only in Feb 2014, announced on the list and in the ChangeLog, but as you found it has build number 2, and the kernel it replaced is the original Slackware64 14.1 one with build number 3.

There could have been a confusion between the patch level and the build number.

I don't think that's very important as anyway upgradepkg replaces the current kernel by the one you tell you to regardless or their respective versions. This is what is written in the "Welcome to Linux (Slackware 14.1)!" mail from PV:

Welcome to the club.
http://www.linuxquestions.org/questi...ry-4175504331/
http://www.linuxquestions.org/questi...on-4175520633/
http://www.linuxquestions.org/questi...rs-4175530380/
Essentially it was a small error that occurred when quickly addressing a nasty kernel bug.

Thank you for this explanation :-) Problem solved.